[SERVER-38833] A failure to timestamp a storage transaction requires restarting the transaction Created: 04/Jan/19  Updated: 29/Oct/23  Resolved: 18/Jan/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.0.7, 4.1.8

Type: Bug Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Daniel Gottlieb (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0
Sprint: Storage NYC 2019-01-28
Participants:
Linked BF Score: 0

 Description   

In SERVER-37121, instead of crashing when a commit_timestamp races with the oldest/stable timestamp for the "ready: true" write of a secondary background index build, we changed the behavior to retry.

I incorrectly thought a transaction could be timestamped with a new value if the old one raced with constraints such as the stable_timestamp. However, a failure to timestamp a transaction requires redoing the whole transaction.

Note WT does not return a WT_ROLLBACK error code in this case, which presumably would have resulted in a WriteConflictRetry exception being thrown. Instead WT returns their generic error code.



 Comments   
Comment by Githook User [ 06/Feb/19 ]

Author:

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

Message: SERVER-38833: Throw a WCE when index completion ghost writes set a bad timestamp.

(cherry picked from commit a44f3e0c4d8268f3af8b27bf70b9f0ce93bb8a02)
Branch: v4.0
https://github.com/mongodb/mongo/commit/93c5206608e1c3887c74cc88405a11b155223721

Comment by Githook User [ 18/Jan/19 ]

Author:

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

Message: SERVER-38833: Throw a WCE when index completion ghost writes set a bad timestamp.
Branch: master
https://github.com/mongodb/mongo/commit/a44f3e0c4d8268f3af8b27bf70b9f0ce93bb8a02

Generated at Thu Feb 08 04:50:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.