[SERVER-50618] sharding_statistics_server_status.js should retry its moveChunk operations on ConflictingOperationInProgress Created: 28/Aug/20  Updated: 29/Oct/23  Resolved: 03/Sep/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Bug Priority: Major - P3
Reporter: Matthew Saltz (Inactive) Assignee: Matthew Saltz (Inactive)
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2020-09-07
Participants:
Linked BF Score: 34

 Description   

If this migration aborts on the donor due to an index build, as it's supposed to, but the recipient takes a long time to finish, the subsequent migration can get ConflictingOperationInProgress.

Like SERVER-50545, we may retry the moveChunks in the test here if they fail with ConflictingOperationInProgress.



 Comments   
Comment by Githook User [ 03/Sep/20 ]

Author:

{'name': 'Matthew Saltz', 'email': 'matthew.saltz@mongodb.com', 'username': 'saltzm'}

Message: SERVER-50618 Make sharding_statistics_server_status.js retry moveChunk commands on ConflictingOperationInProgress (patch 2)
Branch: master
https://github.com/mongodb/mongo/commit/1cad5256f939929a40fa53074bb7a502ece9f623

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