-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2017-12-18, Repl 2018-01-01, Repl 2018-01-15
Secondaries replicating CRUD operations assign timestamps to those updates for the purpose of reading data at a timestamp.
For recover to a timestamp, writes (only metadata?) resulting from replicating commands need to be timestamped as well.
The scope of this ticket is to fix all of the easy cases and file tickets for additional commands that are troublesome. SERVER-30911 already exists for index builds.
- depends on
-
SERVER-32187 Metadata changes on secondaries don't advance the min majority read timestamp enough
- Closed
- is related to
-
SERVER-30809 Investigating remaining writes to the [KV]Catalog that must be timestamped.
- Closed
-
SERVER-31086 adorn secondary inserts and vector inserts with timestamps
- Closed
-
SERVER-31087 adorn secondary updates with timestamps
- Closed
-
SERVER-31088 adorn secondary deletes with timestamps
- Closed
-
SERVER-31260 Adorn secondary upserts with timestamps
- Closed
- related to
-
SERVER-30911 Apply timestamps for index build writes
- Closed
-
SERVER-32128 Test that all collections have UUIDs on clean startup in master branch and disable/remove all other parts of set_schema_version.js.
- Closed