[SERVER-42185] cleanUpAfterBuild can be called after the node steps down to secondary Created: 11/Jul/19  Updated: 29/Oct/23  Resolved: 18/Jul/19

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

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

Issue Links:
Backports
Depends
Related
related to SERVER-42799 obtain timestamp for cleaning up inde... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2
Sprint: Execution Team 2019-07-15
Participants:
Linked BF Score: 62

 Description   

It seems cleanUpAfterBuild can be called after the primary steps down to the secondary. In that case, we would end up having an untimestamped write to the catalog because this wouldn't get executed.



 Comments   
Comment by Eric Milkie [ 22/Jul/19 ]

commit 15cb55efacbb7be6d3bd65ea265b1c45da5decff
Author: Eric Milkie <milkie@10gen.com>
Date: Tue Jul 16 10:43:08 2019 -0400

SERVER-42185 timestamp index build cancellation correctly, including at stepdown time

(cherry picked from commit a4f07aed5277cb31d2422b3dc658b5758d1773ed)
Branch: 4.2

Comment by Githook User [ 18/Jul/19 ]

Author:

{'name': 'Eric Milkie', 'username': 'milkie', 'email': 'milkie@10gen.com'}

Message: SERVER-42185 timestamp index build cancellation correctly, including at stepdown time
Branch: master
https://github.com/mongodb/mongo/commit/a4f07aed5277cb31d2422b3dc658b5758d1773ed

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