Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1574
@revans2
IMO this patch will still work if we address both of the expectations: 1)
BlobStore should list keys for all available keys for listing keys. 2)
BlobStore should ensure that it will pull from another replica when blob is not
in local. If we address only 1) it will break this patch and go back to now.
Suppose both things are achieved, we would like to have nimbus giving up
leadership rather than crash when we have zero replication count on one of
topologies code in blobstore. Like we talked we don't want to crash Nimbus in
this case, since itself is a replica of blobstore, so it incurs decreasing
replication count of some part of blobs, and next leader nimbus has more chance
to crash.
But also as you said there should be few problem if we have enough nimbuses
and syncing up blobs is enough fast and done often.
---
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.
---
