-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
ALL
-
Execution Team 2025-02-17
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When using a mock replication coordinator, namely in unit tests, we always update the committed snapshot to this timestamp if it is higher. However, this is not necessarily correct as there may be an outstanding writes to the oplog before this one which have not yet committed. Thus, the committed snapshot may erroneously contain oplog holes until those outstanding writes commit.
- is depended on by
-
SERVER-98583 Make ReshardingRecipientService count the number of documents in "strict-consistency" state
-
- Closed
-
-
SERVER-98584 Make ReshardingDonorService count the number of documents in the "blocking-writes" state
-
- Closed
-