Resolve listener passed to WriteActionReplicasProxy#failShardIfNeeded when replica not failed #12181
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
On write operations we do not fail the replicas if the primary has been closed. However in this case we are never resolving the listener passed to ReplicasProxy. This can leave write requests open as
pendingActions
is never decref'd to 0 inside ReplicaOperation.I found this while debugging #12114. The requests that are left open are start_recovery and retention_lease_sync. retention_lease_sync is a write operation that occurs as a step in recovery. The recovery is cancelled and primary shut down while there is an ongoing sync. The sync will hit this condition where the primary is shut down before the req is ack'd and closed on the node, leaving both the sync and original recovery req open.
leaving as draft for now will try and write a more thorough integ test of this case.
Related Issues
Resolves #12114
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.