Removes race condition cluster get pid issue 1131 #1140
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
|
|
|
I am curios if this project still alive? or not? |
|
yeah, same question here. @rogeralsing do you have any information about the project's current state? |
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.
I read the contributing.md and followed the steps
Added tests for manager in disthash
TestManagerConcurrentAccess simulates the race condition by spawning two goroutines - one updates topology continuously while another performs identity lookups, verifying no data races occur under concurrent read/write operations to the rdv field.
TestConcurrentClusterOperations creates a 3-node cluster and performs 100 concurrent identity lookups across different nodes
The tests reveal there is a lot of different data races but no longer in onClusterTopology and get.