[Core]Add filesystem catalog lock #2867
Closed
Conversation
This file contains 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
|
@TaoZex In fact, what we want is not a filesystem lock, but to optimize the catalog lock interface and support configuring catalog lock in the filesystem catalog. This will be quite different from the implementation of this PR. |
Thanks for your reply, I will close this pr. |
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.
Purpose
When a process in file system attempts to acquire a lock, it tries to create a specific file in the file system. The existence of this file represents the state of the lock. If the file does not exist, it indicates that the lock is available, and the process can successfully acquire the lock. If the file already exists, it indicates that the lock has been acquired by another process.
subtask of #2824
Tests
API and Format
Documentation