-
Notifications
You must be signed in to change notification settings - Fork 3.7k
branch-3.0: [Fix](remote-fs)Change closed Field to Instance-Level to Avoid Global Shutdown Issues in RemoteFileSystem #48351 #48378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
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
… Shutdown Issues in RemoteFileSystem (#48351) ### PR Description: Change Background: The closed field in the current RemoteFileSystem class is static, meaning it is shared globally across all instances of the class. This design leads to issues when multiple parts of the application use RemoteFileSystem and attempt to close it. Once one instance is closed, the static closed field is set to true, causing other instances to incorrectly report that the file system is unavailable. This can cause confusion and inconsistent behavior, especially when multiple threads are involved. ### Change Details: closed Field: The closed field has been moved from a static field to an instance-level field. This ensures that each RemoteFileSystem instance maintains its own shutdown status, eliminating the problem of shared state between instances.
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Contributor
|
run buildall |
TPC-H: Total hot run time: 39983 ms |
TPC-DS: Total hot run time: 199846 ms |
ClickBench: Total hot run time: 33.75 s |
dataroaring
approved these changes
Feb 26, 2025
Contributor
dataroaring
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Contributor
Author
|
PR approved by at least one committer and no changes requested. |
Contributor
Author
|
PR approved by anyone and no changes requested. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Cherry-picked from #48351