[SERVER-78318] ConfigsvrCollMod command should not support retryable writes Created: 22/Jun/23  Updated: 29/Oct/23  Resolved: 30/Aug/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Silvia Surroca Assignee: Pol Pinol
Resolution: Fixed Votes: 0
Labels: car-71-backport-declined, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-77633 Calling withTransaction with a checke... Closed
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-09-04
Participants:

 Description   

The ConfigsvrCollMod command currently is marked as supporting retryable writes (here).

However, if that command is called with retryWrites:true, the config server could end up in a deadlock due to SERVER-77633.

Currently, there is no one calling ConfigsvrCollMod with retryWrites:true, that's why this is not actually a bug.

The purpose of this ticket is to remove the support for retryable writes on that command to avoid its future use.



 Comments   
Comment by Githook User [ 30/Aug/23 ]

Author:

{'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}

Message: SERVER-78318 ConfigsvrCollMod command should not support retryable writes
Branch: master
https://github.com/mongodb/mongo/commit/c5c3086dcae61481f80664f1de1dcd965aee2147

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