[
https://issues.apache.org/jira/browse/STORM-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190903#comment-15190903
]
ASF GitHub Bot commented on STORM-1620:
---------------------------------------
GitHub user srdo opened a pull request:
https://github.com/apache/storm/pull/1205
STORM-1620: Update curator to fix CURATOR-209
See https://issues.apache.org/jira/browse/STORM-1620
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/srdo/storm update-curator
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/1205.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 #1205
----
commit aa424c15f968b3c344418ca3f1bf0c0a397e1d26
Author: Stig Døssing <[email protected]>
Date: 2016-03-11T13:13:58Z
STORM-1620: Update curator to fix CURATOR-209
----
> Update Curator to fix CURATOR-209
> ---------------------------------
>
> Key: STORM-1620
> URL: https://issues.apache.org/jira/browse/STORM-1620
> Project: Apache Storm
> Issue Type: Bug
> Reporter: Stig Rohde Døssing
> Assignee: Stig Rohde Døssing
>
> Curator 2.6.0-2.9.0 seem to have a bug that can cause them to loop infinitely
> in case of a flaky network. 2.10.0 has a fix.
> See
> https://issues.apache.org/jira/browse/CURATOR-209?focusedCommentId=14998304&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14998304
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
