[SERVER-73686] Make ShardsvrDropCollectionIfUUIDNotMatching take write concern majority in resharding coordinator Created: 06/Feb/23  Updated: 29/Oct/23  Resolved: 27/Feb/23

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 5.0.4, 6.0.0, 6.3.0-rc0
Fix Version/s: 7.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Blake Oler Assignee: Marcos José Grillo Ramirez
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-54231 Resharding can leave behind local col... Closed
is related to SERVER-60007 Implement command to drop collection ... Closed
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2023-03-06
Participants:

 Description   

This change is necessary. Without this, the replica set shard can go into rollback and cause the dropped collection(s) to come back to life.

Offending lines of code



 Comments   
Comment by Githook User [ 27/Feb/23 ]

Author:

{'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-73686 Change ShardsvrDropCollectionIfUUIDNotMatching to take only majority write concern
Branch: master
https://github.com/mongodb/mongo/commit/c1f4225e0c0f818041a9f15be4945986227f7328

Comment by Blake Oler [ 07/Feb/23 ]

Since doing this work won't in the immediate future simplify the resharding coordinator, I've decided to assign it back to the sharding backlog.

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