[
https://issues.apache.org/jira/browse/STORM-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14960797#comment-14960797
]
ASF GitHub Bot commented on STORM-1115:
---------------------------------------
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/802#issuecomment-148734244
@danielschonfeld It looks fine to me. Personally am +1 on it, but I want
to hear back from @Parth-Brahmbhatt. He has a concern about unnecessary log
statements. I assume that these are coming directly out of curator itself, so
I am not really sure how he wants to handle this.
> 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)
