-
Type: Task
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Storage
-
None
-
Replication
-
Execution Team 2020-06-29
This work is the result of adding waiting for the truncate point in SERVER-46186.
The code design should be made with consideration to SERVER-45847 and SERVER-45792. Currently we do not obey writeConcern's wtimeout for flushing the journal or waiting for the truncate point (the oplog no holes point).
This ticket must also unmodify the majority_writes_wait_for_all_durable_timestamp.js test that SERVER-46186 modified to explicitly use
to get a writeConcern wtimeout to work.
- related to
-
SERVER-45792 Make StorageEngine::waitForJournalFlush interruptible
- Closed
-
SERVER-45847 Pull the JournalFlusher out of the storage engine layer and place it above the storage engine
- Closed