You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@eagle.apache.org by "Su Ralph (JIRA)" <ji...@apache.org> on 2016/11/08 13:16:58 UTC

[jira] [Resolved] (EAGLE-675) AlertEngine: don't host long-live curator framework for schedule

     [ https://issues.apache.org/jira/browse/EAGLE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Su Ralph resolved EAGLE-675.
----------------------------
    Resolution: Fixed

> 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)