-
-
Notifications
You must be signed in to change notification settings - Fork 171
Add minLamport for proper GC of deactivated clients #1060
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
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
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.
💡 Codebase verification
Based on the search results, I can now provide a final response:
Issue #1058 needs to be fixed to properly cleanup version vectors during client deactivation
The commented test code in
test/integration/gc_test.goreveals that when a client is deactivated, its version vector is not being properly removed from the database. This is a critical issue because:d2.VersionVector()length to be 1 after deactivation, but it remains at 2The implementation in
server/backend/database/mongo/client.goshows that while client status is updated to "deactivated", there's no corresponding cleanup of the version vector.🔗 Analysis chain
Critical issue: Version vector cleanup after client deactivation
The TODO comments reference issue #1058 which affects the proper cleanup of version vectors after client deactivation. This is a critical issue as it impacts garbage collection efficiency.
Let's verify if this issue has been addressed in other parts of the codebase:
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
Length of output: 2013
Script:
Length of output: 201937
Script:
Length of output: 1770
Script:
Length of output: 12616