[ https://issues.apache.org/jira/browse/EAGLE-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15621609#comment-15621609 ]
ASF GitHub Bot commented on EAGLE-701: -------------------------------------- GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/586 [EAGLE-701] AlertEngine: bolt should check ZK for latest spec when start You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-701 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/586.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 #586 ---- commit bd6ac1d74a6c71bf7bde8046c06266c0afeb1988 Author: wujinhu <wujinhu...@126.com> Date: 2016-10-31T08:28:35Z AlertEngine: bolt should check ZK for latest spec when start ---- > AlertEngine: bolt should check ZK for latest spec when start > ------------------------------------------------------------ > > Key: EAGLE-701 > URL: https://issues.apache.org/jira/browse/EAGLE-701 > Project: Eagle > Issue Type: Improvement > Affects Versions: v0.5.0 > Reporter: Su Ralph > Assignee: wujinhu > Fix For: v0.5.0 > > > Currently, bolt use zk listening for metadata reload only. > This require zk to be periodically updated. In the case of bolt down, and > storm start bolt another place(vm, process), if the zk is not updated, then > new bolt possibly can not get the metadata to work well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)