[SERVER-61416] Indefinitely retry errors in rename coordinator Created: 11/Nov/21  Updated: 29/Oct/23  Resolved: 19/Nov/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 5.1.0, 5.0.3
Fix Version/s: 5.2.0, 5.1.2, 5.0.6

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
is related to SERVER-65340 Operations hang when re-using dropped... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.1, v5.0
Sprint: Sharding EMEA 2021-11-29
Participants:

 Description   

DDL coordinators share a common retry logic that enumerates the exceptions that must be retried. All other errors result in the operation being interrupted and the coordinator getting released.

Since the rename coordinator must never be released in case of unexpected errors, add a specialized logic to indefinitely retry the execution.



 Comments   
Comment by Githook User [ 30/Nov/21 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-61416 Indefinitely retry errors in rename coordinator
Branch: v5.0
https://github.com/mongodb/mongo/commit/f065213ee9149bf063f55f90c57d4c739362d3c3

Comment by Githook User [ 29/Nov/21 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-61416 Indefinitely retry errors in rename coordinator
Branch: v5.1
https://github.com/mongodb/mongo/commit/e776d32a970cd7f82bb44ea2d1ce185f404c387e

Comment by Githook User [ 19/Nov/21 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-61416 Indefinitely retry errors in rename coordinator
Branch: master
https://github.com/mongodb/mongo/commit/872e93521fe353984802a9bcab0d421549914117

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