[Fix][Zeta] Fix double-checked locking without volatile in HdfsStorage #9200
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.
Purpose of this pull request
This pull request addresses two issues identified in the HDFS checkpoint storage code:
Does this PR introduce any user-facing change?
No
How was this patch tested?
This patch primarily involves minor changes to logging and the addition of the volatile keyword to a field. Given the nature of these changes, no new test cases were added. The existing test suite covers the functionality of the HdfsStorage class, and these changes do not introduce new logic that requires additional testing.
The changes made are:
Logging Improvements: Enhanced log messages for better clarity and debugging.
Volatile Keyword: Added the volatile keyword to ensure visibility of changes to the fs field across threads.
These modifications are unlikely to affect the existing behavior, and thus, the existing test cases are sufficient to validate the changes.
Check list
New License Guide
release-note.