[
https://issues.apache.org/jira/browse/EAGLE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647451#comment-15647451
]
ASF GitHub Bot commented on EAGLE-675:
--------------------------------------
GitHub user RalphSu opened a pull request:
https://github.com/apache/incubator-eagle/pull/626
EAGLE-675 : AlertEngine: don't host long-live curator framework for s…
…chedule
Author: ralphsu
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/RalphSu/incubator-eagle master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-eagle/pull/626.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 #626
----
commit 715a8f7a5f02fc7fb59af3816f1711a65b2150ab
Author: Ralph, Su <[email protected]>
Date: 2016-11-08T12:31:57Z
EAGLE-675 : AlertEngine: don't host long-live curator framework for schedule
Author: ralphsu
----
> AlertEngine: don't host long-live curator framework for schedule
> ----------------------------------------------------------------
>
> Key: EAGLE-675
> URL: https://issues.apache.org/jira/browse/EAGLE-675
> Project: Eagle
> Issue Type: Bug
> Affects Versions: v0.5.0
> Reporter: Su Ralph
> Assignee: Su Ralph
> Fix For: v0.5.0
>
>
> In Coordinator, the config bus producer is hold as member. This is try to
> reuse connection for continous operation. But this is buggy, since when zk
> server in network issue, curator framework would generate a lot of logs that
> flood the log file.
> Same for ExclusiveExecutor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
