[SERVER-71305] Legacy shard collection path waits on wrong opTime to be majority committed (5.0 and older) Created: 14/Nov/22  Updated: 29/Oct/23  Resolved: 17/Nov/22

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

Type: Bug Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Pol Pinol
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2022-11-14, Sharding EMEA 2022-11-28
Participants:
Linked BF Score: 55

 Description   

Similarly to SERVER-56556, the 4.4 legacy shard collection patch waits for majority write concern after creating the shard index.

The problem is that if the index was already created no write will be performed , in this case the last op time on the current client could be a very old op time, associated with the last write performed by a previous operation.



 Comments   
Comment by Githook User [ 16/Nov/22 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-71305 Legacy shard collection path waits on wrong opTime to be majority committed
Branch: v5.0
https://github.com/mongodb/mongo/commit/31b94b67c87cece2136e3b666eb5e55ef7349e84

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