[SERVER-45147] "Ghost" timestamp must set transaction to unordered Created: 13/Dec/19  Updated: 29/Oct/23  Resolved: 20/Mar/20

Status: Closed
Project: Core Server
Component/s: Index Maintenance
Affects Version/s: None
Fix Version/s: 4.2.6, 4.4.0-rc0, 4.7.0

Type: Bug Priority: Major - P3
Reporter: Matthew Russotto 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
Problem/Incident
Related
is related to SERVER-71145 Allow observed all_durable to move ba... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4, v4.2
Sprint: Execution Team 2020-01-13, Execution Team 2020-01-27, Execution Team 2020-02-10, Execution Team 2020-02-24, Execution Team 2020-03-09, Execution Team 2020-03-23, Execution Team 2020-04-06
Participants:
Linked BF Score: 23

 Description   

When we cancel an index build, we do some writes at a "ghost" timestamp (one which may or may not correspond to an oplog entry). The existence of this "ghost" timestamp may hold oplog visibility back, so when we complete the write we need to trigger oplog visibility to be refreshed. That only happens if the transaction is set to unordered (setOrderedCommit(false)).



 Comments   
Comment by Githook User [ 26/Mar/20 ]

Author:

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

Message: SERVER-45147: Ensure ghost timestamped transactions trigger the stable timestamp to advance when they commit/abort. Ensure the durable timestamp does not move backwards.

(cherry picked from commit 5ab625013bcf6438515dceb5fe7c2228257cb863)
Branch: v4.2
https://github.com/mongodb/mongo/commit/45bb9b5b2075f30068c4de7d8c1a5555333a6590

Comment by Githook User [ 20/Mar/20 ]

Author:

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

Message: SERVER-45147: Ensure ghost timestamped transactions trigger the stable timestamp to advance when they commit/abort. Ensure the durable timestamp does not move backwards.

(cherry picked from commit 5ab625013bcf6438515dceb5fe7c2228257cb863)
Branch: v4.4
https://github.com/mongodb/mongo/commit/3d430b974fca9c453db0463dad0747f31cb94bb1

Comment by Githook User [ 20/Mar/20 ]

Author:

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

Message: SERVER-45147: Ensure ghost timestamped transactions trigger the stable timestamp to advance when they commit/abort. Ensure the durable timestamp does not move backwards.
Branch: master
https://github.com/mongodb/mongo/commit/5ab625013bcf6438515dceb5fe7c2228257cb863

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