There's a circular dependency between the db/repl/oplog and db/transaction libraries that's currently addressed by the getNextOpTimes shim in db/repl/oplog_shim. This circular dependency can be addressed by moving the oplog time reservation logic into its own library.
- is duplicated by
-
SERVER-40508 Move LocalOplogInfo into its own library
-
- Closed
-
- is related to
-
SERVER-43978 Stable timestamp is not being recalculated after aborting oplog holes
-
- Closed
-
- related to
-
SERVER-56453 move LocalOplogInfo out of db/repl to db/catalog
-
- Closed
-