[SERVER-56556] create collection coordinator waits on wrong opTime to be mojority committed Created: 01/May/21  Updated: 29/Oct/23  Resolved: 01/May/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: Backlog
Fix Version/s: 5.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Tommaso Tocci
Resolution: Fixed Votes: 0
Labels: PM-1965-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-54905 Implement FSMs hierarchy testing conc... Closed
is depended on by SERVER-56555 Enable drop_collection_sharded.js FSM... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

Create collection coordinator explicitly wait for majority write concern after creating the shard key 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 task scheduled on that thead.
In fact the client associated with a thread of the POS pool is instantiated on thread creation and is reused by different tasks.

So the solution would be to properly set the last op time before to wait it to be majority written.



 Comments   
Comment by Githook User [ 01/May/21 ]

Author:

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

Message: SERVER-56556 create collection coordinator waits on wrong opTime to be mojority committe
Branch: master
https://github.com/mongodb/mongo/commit/e345b88ddca4ec85dc59768647be2e531e490e04

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