[SERVER-30911] Apply timestamps for index build writes Created: 31/Aug/17  Updated: 30/Oct/23  Resolved: 13/Feb/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 3.7.3

Type: Task Priority: Major - P3
Reporter: Eric Milkie Assignee: Daniel Gottlieb (Inactive)
Resolution: Fixed Votes: 0
Labels: rollback-functional
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on WT-3786 Transactions with timestamps should r... Closed
is depended on by SERVER-32284 awaitReplication can hang when the op... Closed
Related
is related to SERVER-30809 Investigating remaining writes to the... Closed
is related to SERVER-32188 Have secondaries apply timestamps to ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2017-12-18, Repl 2018-01-01, Repl 2018-01-15, Repl 2018-01-29, Repl 2018-02-12, Repl 2018-02-26
Participants:

 Comments   
Comment by Githook User [ 13/Feb/18 ]

Author:

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

Message: SERVER-30911: Timestamp index build start and completion.
Branch: master
https://github.com/mongodb/mongo/commit/bb1a895bf84fdeb1e0ef084fd40160f2f694e05d

Comment by Eric Milkie [ 01/Sep/17 ]

Looks like you can just call getClusterTime() on the logical clock to get a timestamp to use for the initial index writes.

Comment by Eric Milkie [ 01/Sep/17 ]

We believe all that is necessary here is to timestamp the initial index writes with the last timestamp that was currently reserved (no need to reserve a new timestamp).

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