[SERVER-47761] moveChunk command in stepdown suites should be retried on CallbackCanceled error response Created: 24/Apr/20  Updated: 29/Oct/23  Resolved: 27/Apr/20

Status: Closed
Project: Core Server
Component/s: Sharding, Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.4.0-rc4, 4.7.0

Type: Task Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Gregory Noma
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
is related to SERVER-42192 Write a concurrency workload to test ... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4
Sprint: Sharding 2020-05-04
Participants:
Linked BF Score: 26

 Description   

It is possible for a moveChunk command to receive a CallbackCanceled error response when the node is shutting down. We should have the network_error_and_txn_override.js override retry running the moveChunk command on a CallbackCanceled error response so it can learn the definitive result of the operation, similar to what we do with the shardCollection command already.



 Comments   
Comment by Githook User [ 28/Apr/20 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-47761 Retry moveChunk in stepdown suites on CallbackCanceled

(cherry picked from commit 53fbcd81aa71a5d5289fdc27dffe47f174039e5e)
Branch: v4.4
https://github.com/mongodb/mongo/commit/a442e48115903835f3af75aeb43bc4f689423d1f

Comment by Githook User [ 27/Apr/20 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-47761 Retry moveChunk in stepdown suites on CallbackCanceled
Branch: master
https://github.com/mongodb/mongo/commit/53fbcd81aa71a5d5289fdc27dffe47f174039e5e

Generated at Thu Feb 08 05:15:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.