Clear the metadata cache when setting FORCE_CHECKSUM_AND_WRITE #2481
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixing the issue that md5 files not in the static group, ref: https://issues.redhat.com/browse/MMENG-4250
When we publish FileEvent via Kafka, we need to calculate the checksum, but that picks CALCULATE_NO_WRITE, which means there is no checksum files generated at all, and the info is cached. Then when user request the checksum files, it says it exists as the cache value but actually there is no file in storage, which cause the failure as the jira issue mentioned:
Message: Path io/dropwizard/metrics/metrics-jmx/4.2.28/metrics-jmx-4.2.28.jar.md5 is not available in store