Minimize race in PSSM to optimize shard sync calls #1088
Merged
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.
Description of changes:
There exists a race condition between
PeriodicShardSyncManager (PSSM)
andScheduler
as reads and writes can happen concurrently in the respective threads. This would cause unnecessary shard syncs for example whenPSSM
is initiated at the same time as theScheduler
the streamToLease map is filtered based on the previous snapshot of thecurrentStreamConfigMap
which tricks thePSSM
into believing that there is no leases for the newly added streams that already have leases.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.