Details
-
Task
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
Attachments
Issue Links
- depends on
-
SERVER-84195 Handle the new lastWritten opTime in OplogQueryMetadata
-
- Open
-
-
SERVER-85723 Update metrics related to lastWritten opTime
-
- Open
-
-
SERVER-84196 Use lastWritten instead of lastApplied to decide if a node can vote for an election candidate
-
- Backlog
-
-
SERVER-85704 Use lastWritten opTime for to wait for afterClusterTime/atClusterTime on secondaries
-
- Backlog
-
-
SERVER-85705 Use lastWritten opTime for sync source selection
-
- Backlog
-
-
SERVER-85702 Use lastWritten opTime for secondary's term check when learning the commit point
-
- In Code Review
-
-
SERVER-85703 Use min(lastDurable, lastApplied) to wait for non-majority write concerns with j=true
-
- In Progress
-
-
SERVER-83093 Add functions in replication coordinator to read and update lastWritten timestamp
-
- Closed
-
-
SERVER-83572 Update the lastWritten opTime for startup and primary writes
-
- Closed
-
-
SERVER-83573 Update the lastWritten opTime during secondary modes
-
- Closed
-
-
SERVER-83725 Cleanup setMyLast(Durable|Applied)OpTimeAndWallTime in ReplicationCoordinator
-
- Closed
-
-
SERVER-84188 Add lastWritten opTime to replSetUpdatePosition command
-
- Closed
-
-
SERVER-84189 Update members with the new lastWritten opTime in replSetUpdatePosition
-
- Closed
-
-
SERVER-84190 Add lastWritten opTime to replication heartbeat responses
-
- Closed
-
-
SERVER-84191 Handle the new lastWritten opTime in the heartbeat response
-
- Closed
-
-
SERVER-84192 Add lastWritten opTime to OplogQueryMetadata
-
- Closed
-
-
SERVER-85700 Use lastWritten opTime for journal flush token calculation on secondaries.
-
- Closed
-
-
SERVER-85701 Use lastWritten opTime for commit point calculation when writeConcernMajorityJournalDefault is false
-
- Closed
-