[
https://issues.apache.org/jira/browse/STORM-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14960760#comment-14960760
]
ASF GitHub Bot commented on STORM-1115:
---------------------------------------
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/802#issuecomment-148728541
@danielschonfeld the test failure is because we have too many tests that
don't use ephemeral ports. In all likelihood the JDK8 test was running on the
same box at the same time and got the port before this test could. JDK8 tends
to run through tests faster then JDK7 does.
> 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)
