feat: prevent multiple servers on the same index directory#26
Merged
Conversation
Add an exclusive file lock (serve.lock) acquired at server startup using the fs2 crate. If another tgrep server already holds the lock, the second server exits immediately with a clear error message including the existing server's PID and port. The lock is held for the lifetime of the server process and automatically released on exit (normal shutdown, crash, or kill). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
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.
Summary
Prevents multiple
tgrep serveinstances from running on the same index directory, which could cause index corruption andserve.jsonoverwrites.Changes
try_acquire_server_lock()using fs2 crate for cross-platform exclusive file locking onserve.lockBehavior
When a second server attempts to start on the same index directory:
The lock is held for the server lifetime and automatically released on exit (normal, crash, or kill).