Mikhail-Aoun commented on issue #7653:
URL: https://github.com/apache/storm/issues/7653#issuecomment-5660771871

   The test completed successfully with those fixes backported to our Storm 
2.8.9 version. We no longer have those unexpected `dep-apeframework*` JARs in 
the blobstore.
   
   For your information, according to the logs from my execution, it seems that 
the `dep-apeframework*` JAR download attempt is now successfully caught by this 
exception:
   
   ```text
   2026-09-13 18:14:37.179 o.a.s.d.n.Nimbus [INFO] Removing dependency blobs of 
val-ipc-fci-nrt_Fir-RCFD_2017100_0143-4215-1789322971 - 
[dep-apeframework-0.0.11710-SNAPSHOT-03c571ab-94dd-4925-b1d3-0cc73b3c9a77.jar]
   2026-09-13 18:14:37.211 o.a.s.d.n.Nimbus [WARN] begin blob download 
exception.
   
KeyNotFoundException(msg:dep-apeframework-0.0.11710-SNAPSHOT-03c571ab-94dd-4925-b1d3-0cc73b3c9a77.jar)
           at 
org.apache.storm.blobstore.LocalFsBlobStore.getStoredBlobMeta(LocalFsBlobStore.java:273)
           at 
org.apache.storm.blobstore.LocalFsBlobStore.getBlob(LocalFsBlobStore.java:406)
           at 
org.apache.storm.daemon.nimbus.Nimbus.beginBlobDownload(Nimbus.java:4124)
           at 
org.apache.storm.generated.Nimbus$Processor$beginBlobDownload.getResult(Nimbus.java:4753)
           at 
org.apache.storm.generated.Nimbus$Processor$beginBlobDownload.getResult(Nimbus.java:4724)
           at 
org.apache.storm.thrift.ProcessFunction.process(ProcessFunction.java:40)
           at 
org.apache.storm.thrift.TBaseProcessor.process(TBaseProcessor.java:41)
           at 
org.apache.storm.security.auth.SimpleTransportPlugin$SimpleWrapProcessor.process(SimpleTransportPlugin.java:171)
   ```
   
   I’ll get back to you if the problem happens again, but I think this fix has 
solved it. Thanks again for the update!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to