Github user revans2 commented on the issue:
https://github.com/apache/storm/pull/1574
The code to do the leader election based off of the IDs was removed because
architecturally the blobstore should be in charge of maintaining high
availability. Exposing what is stored on the local disk in an implementation
detail and exposing that to nimbus breaks a lot of things. Not to mention is
not really possible with some blobstore implementations, like the HDFS backed
one.
To offset this we made sure that you could access the version of the blob
even if it is stored on a different instance of the blobstore.
Additionally the old code did not guarantee consistency either. There was
a timeout where if nimbus waited long enough to get a copy of all of the items
it gave up and would still become leader. If there really is no guarantee why
add in the extra overhead?
---
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.
---
