Github user agresch commented on the issue:
https://github.com/apache/storm/pull/2618
Couple of comments back to @revans2 from Apr5.....
1) We don't delete the blobs on the nimbus side for a while after we kill
the topology. - Would we also prevent the user from doing so in this case?
2) We don't output the stack trace until it has failed some number of times
in a row. - This may be fine for the supervisor, but I see this exception
trace polluting the nimbus log non-stop. Would you prevent this as well?
2018-06-25 21:49:03.928 o.a.s.d.n.Nimbus pool-37-thread-483 [WARN] get blob
meta exception.
org.apache.storm.utils.WrappedKeyNotFoundException:
run-1-1529962766-stormjar.jar
at
org.apache.storm.blobstore.LocalFsBlobStore.getStoredBlobMeta(LocalFsBlobStore.java:256)
~[storm-server-2.0.0.y.jar:2.0.0.y]
at
org.apache.storm.blobstore.LocalFsBlobStore.getBlobMeta(LocalFsBlobStore.java:286)
~[storm-server-2.0.0.y.jar:2.0.0.y]
at
org.apache.storm.daemon.nimbus.Nimbus.getBlobMeta(Nimbus.java:3498)
[storm-server-2.0.0.y.jar:2.0.0.y]
at
org.apache.storm.generated.Nimbus$Processor$getBlobMeta.getResult(Nimbus.java:4014)
[storm-client-2.0.0.y.jar:2.0.0.y]
at
org.apache.storm.generated.Nimbus$Processor$getBlobMeta.getResult(Nimbus.java:3993)
[storm-client-2.0.0.y.jar:2.0.0.y]
at
org.apache.storm.thrift.ProcessFunction.process(ProcessFunction.java:38)
[shaded-deps-2.0.0.y.jar:2.0.0.y]
at
org.apache.storm.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
[shaded-deps-2.0.0.y.jar:2.0.0.y]
at
org.apache.storm.security.auth.sasl.SaslTransportPlugin$TUGIWrapProcessor.process(SaslTransportPlugin.java:147)
[storm-client-2.0.0.y.jar:2.0.0.y]
at
org.apache.storm.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:291)
[shaded-deps-2.0.0.y.jar:2.0.0.y]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[?:1.8.0_131]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[?:1.8.0_131]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]
---
