The JournalFlusher creates an OperationContext and runs a data flush before pausing for unit testing until a request comes in. There is already a flag for the JournalFlusher, created to stop the JournalFlusher from running until requested, specially added to make it only run upon request in unit testing. However, it doesn't stop it from running an initial flush and needs to be expanded to do so.
- is duplicated by
-
SERVER-53815 NamespaceMetadataChangeNotificationsTest, and other sharding unit test fixtures, call ServiceContext::setTickSource() after the JournalFlusher, which uses the TickSource, is started in ServiceContextMongoDTest
-
- Closed
-