[SERVER-42799] obtain timestamp for cleaning up index build without noop write Created: 13/Aug/19  Updated: 29/Oct/23  Resolved: 22/Aug/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.2.1, 4.3.1

Type: Improvement Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
is related to SERVER-34172 Turn primary index build ghost writes... Closed
is related to SERVER-42185 cleanUpAfterBuild can be called after... Closed
is related to SERVER-42621 3 way deadlock can happen between hyb... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.2
Sprint: Execution Team 2019-08-26
Participants:
Linked BF Score: 12

 Description   

After SERVER-42185, index build cancellations may be timestamped in one of two ways:

We should consider converging on using ghost timestamps for cancellations.

Additionally, we may tweak index build cleanup to release the RSTL lock in SERVER-42621. This makes the first method (SERVER-34172) redundant.



 Comments   
Comment by Githook User [ 28/Aug/19 ]

Author:

{'email': 'benety@mongodb.com', 'name': 'Benety Goh', 'username': 'benety'}

Message: SERVER-42799 obtain timestamp for cleaning up index build without noop write

(cherry picked from commit 283e8966d1b24559963c460591b1cb845e4c6f9a)
Branch: v4.2
https://github.com/mongodb/mongo/commit/bf41d49a77695d50479aa37902a4e622a01bc37f

Comment by Githook User [ 22/Aug/19 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-42799 obtain timestamp for cleaning up index build without noop write
Branch: master
https://github.com/mongodb/mongo/commit/283e8966d1b24559963c460591b1cb845e4c6f9a

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