Github user revans2 commented on the issue:
https://github.com/apache/storm/pull/2618
I am trying to understand the reasons behind this change. Is this jira
just to remove an exception that shows up in the logs? Or is that exception
actually causing a problem?
The reason I ask is a risk vs reward situation. The code in AsyncLocalizer
is really very complicated and because it is asynchronous there are lots of
races and corner cases. This makes me a bit nervous to start changing
fundamental things just because of some extra logs. Additionally this is a
distributed system and this particular race is inherent in the system. It is
possible for someone to delete a blob at any point in time and the code in the
supervisor needs to handle it.
---
