-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
Fully Compatible
-
v4.0, v3.6
-
Storage NYC 2019-03-25, Storage NYC 2019-04-08, Storage NYC 2019-04-22
This ticket is split out from SERVER-34598. SERVER-40080 will now be used to track the patch to include wall clock times corresponding to the lastApplied and lastDurable optimes only. The tasks required for SERVER-40080 and SERVER-40078 are different, and the lastApplied/lastDurable changes are sufficiently complex on their own.
The current plan for implementing this follows. Since SERVER-40080 allows each member of a replica set to track its own last applied and last durable wall clock times, they can communicate this information to the primary similarly to how they communicate their OpTime information (i.e., through replSetUpdatePosition, heartbeats, etc.) so the majority committed wall clock time can be calculated similarly to the way the majority committed OpTime is calculated.
- depends on
-
SERVER-40080 Add lastApplied and lastDurable wall clock times to replSetGetStatus optimes subdocument
- Closed
- is depended on by
-
SERVER-34598 Add millisecond-granularity wallclock times for the various metrics in replSetGetStatus's optimes subdocument
- Closed
- related to
-
SERVER-40353 Add wall clock time corresponding to readConcernMajority OpTime to optimes subdocument
- Closed
-
SERVER-40659 Add regression tests for SERVER-40078
- Closed
-
SERVER-40683 Make wall clock times in replication structures required after 4.2
- Closed
-
SERVER-40737 Use Date_t() as default wallTime value in OpTimeAndWallTimes
- Closed
-
SERVER-42485 Remove FCV checks gating reporting wall clock times in Replication
- Closed
-
SERVER-43465 Remove InvalidBSON try/catch blocks for ReplSetGetStatus wall clock times
- Closed