silent5945 commented on issue #7966: URL: https://github.com/apache/storm/issues/7966#issuecomment-2700587558
Thanks for the feedback, it's really appreciated. We are using `v2.4.0`, and I am certain than absolutely nothing is done to interact with the blobstore, nor with API or filesystem change. That's an interesting relate issue, although this happens systematically outside of Nimbus restart or new leader election. Although that could probably fix it if the version identification is more robust. Do I understand it right with the fact that this blobstore update can only be caused by something external affecting the time of modification of the files on disk, and not some other internal Storm mechanism? -- 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: dev-unsubscr...@storm.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
