replication: fix io-threads possible race by moving waitForClientIO #1422
+3
−2
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.
Fix race with pending writes in replica state transition
The Problem
In #60 (Dual channel replication) a new
connWrite
call was added before thewaitForClientIO
check. This created a race condition where the main thread may attempt to write to a client that could have pending writes in IO threads.The Fix
Moved the
waitForClientIO()
call earlier insyncCommand
, before anyconnWrite
call. This ensures all pending IO operations are completed before attempting to write to the client.