GitHub user arunmahadevan opened a pull request:
https://github.com/apache/storm/pull/2006
STORM-2412: Nimbus isLeader check while waiting for max replication
While using local FS blob store, nimbus goes into a state where it
indefinitely waits for max replication (with max replication wait time set to
-1). At this time its also observed that the nimbus that received the topology
submission is no longer the leader.
While waiting for max replication, nimbus can also do the `isLeader` check
and fail the topology submission if its no longer the leader.
Also added some debug logs to better troubleshoot the race conditions when
it happens.
This is https://github.com/apache/storm/pull/2003 applied to master branch.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/arunmahadevan/storm STORM-2412-master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/2006.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 #2006
----
commit fd7c62ac0b40b4e5be97c76f94e4c1598c55ee53
Author: Arun Mahadevan <[email protected]>
Date: 2017-03-13T12:41:13Z
STORM-2412: Nimbus isLeader check while waiting for max replication
While using local FS blob store, nimbus goes into a state where it
indefinitely waits for max replication (with max replication wait time set to
-1). At this time its also observed that the nimbus that received the topology
submission is no longer the leader.
While waiting for max replication, nimbus can also do the `isLeader` check
and fail the topology submission if its no longer the leader.
Also added some debug logs to better troubleshoot the race conditions when
it happens.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
