[jira] [Commented] (EAGLE-616) AlertEngine: Reduce the connection from alert-service to ZK
[ https://issues.apache.org/jira/browse/EAGLE-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15574820#comment-15574820 ] ASF GitHub Bot commented on EAGLE-616: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/501 > AlertEngine: Reduce the connection from alert-service to ZK > --- > > Key: EAGLE-616 > URL: https://issues.apache.org/jira/browse/EAGLE-616 > Project: Eagle > Issue Type: Bug >Reporter: Zeng, Bryant >Assignee: Zeng, Bryant > > In QA, it used to show too much connection from alert-service to zookeeper. > We only use zk for exclusive lock and spec version notify, should not have so > much connection. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-616) AlertEngine: Reduce the connection from alert-service to ZK
[ https://issues.apache.org/jira/browse/EAGLE-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15571489#comment-15571489 ] ASF GitHub Bot commented on EAGLE-616: -- Github user mizeng commented on the issue: https://github.com/apache/incubator-eagle/pull/501 @RalphSu could you plz help to review? > AlertEngine: Reduce the connection from alert-service to ZK > --- > > Key: EAGLE-616 > URL: https://issues.apache.org/jira/browse/EAGLE-616 > Project: Eagle > Issue Type: Bug >Reporter: Zeng, Bryant >Assignee: Zeng, Bryant > > In QA, it used to show too much connection from alert-service to zookeeper. > We only use zk for exclusive lock and spec version notify, should not have so > much connection. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-616) AlertEngine: Reduce the connection from alert-service to ZK
[ https://issues.apache.org/jira/browse/EAGLE-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15571488#comment-15571488 ] ASF GitHub Bot commented on EAGLE-616: -- GitHub user mizeng opened a pull request: https://github.com/apache/incubator-eagle/pull/501 [EAGLE-616] AlertEngine: Reduce the connection from alert-service to ZK In QA, it used to show too much connection from alert-service to zookeeper. We only use zk for exclusive lock and spec version notify, should not have so much connection. You can merge this pull request into a Git repository by running: $ git pull https://github.com/mizeng/incubator-eagle EAGLE-616 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/501.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #501 commit 30f881d3cb24d167d521d6477e6b728b38c923dd Author: mizengDate: 2016-10-13T09:28:06Z [EAGLE-616] AlertEngine: Reduce the connection from alert-service to ZK > AlertEngine: Reduce the connection from alert-service to ZK > --- > > Key: EAGLE-616 > URL: https://issues.apache.org/jira/browse/EAGLE-616 > Project: Eagle > Issue Type: Bug >Reporter: Zeng, Bryant >Assignee: Zeng, Bryant > > In QA, it used to show too much connection from alert-service to zookeeper. > We only use zk for exclusive lock and spec version notify, should not have so > much connection. -- This message was sent by Atlassian JIRA (v6.3.4#6332)