-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication, Storage
-
Replication
-
0
Storage maintains the stable timestamp and replication maintains the _currentCommittedSnapshot (a holdover from the pre-timestamping days). We could reduce replication complexity and possibly gain some performance benefits by only maintaining it in one place (probably storage). If at some point we are able to read consistently at any timestamp, including mid-oplog-application-batch, then both of these values could likely be removed in favor of the replication commit point.
- depends on
-
SERVER-34489 Enable new format Unique Index via FCV
- Closed
- is related to
-
SERVER-49777 Change _currentCommittedSnapshot to be a timestamp instead of an optime
- Backlog
- related to
-
SERVER-35420 Remove stable optime candidates list from ReplicationCoordinator
- Closed