Fixes the concurrency issue of calling the Next()
proxy target on RRB
#2409
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.
Round Robin Balancer (RRB)
Next()
implementation did not properly use synchronization mechanisms to ensure right values are visible between concurrently executed code entering the same critical section.Previous use of an atomic add to update the index value without also using an atomic load to read it is incorrect use of atomic synchronization (stale values are read in go-routines).
The index value, obviously, depends on the size of the
targets
slice.If between index calculation and getting a value by index from the slice a target was removed and the index pointed to the last element then a panic due to out of bounds will be the result.
Hence, the logic must be guarded with the semaphore.