[SERVER-44451] mongos retry logic doesn't match driver's spec Created: 06/Nov/19  Updated: 29/Oct/23  Resolved: 18/Dec/19

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

Type: Task Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Randolph Tan
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2019-12-16, Sharding 2019-12-30
Participants:

 Description   

SERVER-42908 added the RetriableError category but that included WriteConcernFailed error (until SERVER-41245) which is not in the driver's spec. Unlike driver's retryable write spec, mongos seems to always retry on WriteConcernFailed error (e.g. this unittest).

This ticket is to investigate whether mongos should retry on WriteConcernFailed error and finish this TODO.



 Comments   
Comment by Githook User [ 18/Dec/19 ]

Author:

{'name': 'Randolph Tan', 'email': 'randolph@mongodb.com'}

Message: SERVER-44451 Don't retry on WriteConcernFailure
Branch: master
https://github.com/mongodb/mongo/commit/19b8a234cea0bc9953c43d449d96359048140e50

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