[SERVER-60266] Retry WriteConcernError exceptions in DDL coordinators Created: 28/Sep/21  Updated: 29/Oct/23  Resolved: 29/Sep/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 5.1.0, 5.0.3
Fix Version/s: 5.0.4, 5.1.0-rc0

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
Depends
Related
is related to SERVER-65340 Operations hang when re-using dropped... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.0
Participants:
Linked BF Score: 20

 Description   

A test running on a machine with network problems resulted in a createCollection failure because of a WriteConcernFailed exception. Such error must be included in the ones retriable while performing a DDL in order not to release coordinators half-way.

Objective of this ticket is to add the WriteConcernError category (that includes the above mentioned exception) to the handled errors.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 30/Sep/21 ]

Author:

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

Message: SERVER-60266 Retry WriteConcernError exceptions in DDL coordinators
Branch: v5.0
https://github.com/mongodb/mongo/commit/b04f30cd48466bd7ad9653484810b182e81208b0

Comment by Githook User [ 29/Sep/21 ]

Author:

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

Message: SERVER-60266 Retry WriteConcernError exceptions in DDL coordinators
Branch: master
https://github.com/mongodb/mongo/commit/56e12c4070a6febb5e8f089d76b35040fa066f72

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