[SERVER-54183] Have resharding rollback oplog application transactions that do not replicate data Created: 01/Feb/21  Updated: 29/Oct/23  Resolved: 05/Feb/21

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

Type: Bug Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Daniel Gottlieb (Inactive)
Resolution: Fixed Votes: 0
Labels: PM-234-M3, PM-234-T-oplog-apply
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2021-02-08
Participants:
Story Points: 1

 Description   

Resharding's oplog application is multi-threaded and is susceptible to write skew under snapshot isolation. Resharding does a trick of writing an unreplicated "no-op" to a common document to get a serialization.

However there are cases where this no-op write becomes the only write in the transaction, leaving it untimestamped. This can lead to a mixed-mode update chain in WT that is problematic with durable history.



 Comments   
Comment by Githook User [ 05/Feb/21 ]

Author:

{'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'username': 'dgottlieb'}

Message: SERVER-54183: Rollback resharding operations that are not timestamped.
Branch: master
https://github.com/mongodb/mongo/commit/a6426fb3d85eb859d95c42dcd76a73b91345fbd2

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