[ https://issues.apache.org/jira/browse/STORM-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14960981#comment-14960981 ]
ASF GitHub Bot commented on STORM-1115: --------------------------------------- Github user Parth-Brahmbhatt commented on the pull request: https://github.com/apache/storm/pull/802#issuecomment-148763402 @revans2 The log concerns were from the origin PR that @danielschonfeld which he has fixed but I guess he force pushed the branch. I am +1 on this change too. @danielschonfeld On a side note, can you provide any steps to reproduce this locally? > Stale leader-lock key effectively bans all nodes from becoming leaders > ---------------------------------------------------------------------- > > Key: STORM-1115 > URL: https://issues.apache.org/jira/browse/STORM-1115 > Project: Apache Storm > Issue Type: Bug > Affects Versions: 0.11.0 > Reporter: Daniel Schonfeld > > I believe this curator bug is what's in play causing the above described > situation. > https://issues.apache.org/jira/browse/CURATOR-202 > Whenever we were hit by this bug we'd start seeing problems in submitting > topologies to nimbus, as well as having problems > activating/deactivating/killing topologies. Basically any topology that > utilizes the `is-leader` macro, since no nimbus believes itself to be the > leader based on LeaderLatch.hasLeadership() -- This message was sent by Atlassian JIRA (v6.3.4#6332)