- 
    Type:Task 
- 
    Resolution: Fixed
- 
    Priority:Major - P3 
- 
    Affects Version/s: None
- 
    Component/s: Replication
- 
    None
- 
        Fully Compatible
- 
        v3.4
- 
        Storage 2017-09-11
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
Currently, the optime generator is only accessed via logOp() and logInsertOps() called via an opObserver.
There is a need for being able to obtain (and reserve) optimes prior to opObservers being run; the work for this ticket will be to thread through an interface for obtaining a new block of OpTimes and providing logInsertOps() with these times.
One such need is for transactions that write multiple oplog entries, such as vectored insert.
- is depended on by
- 
                    SERVER-30639 Timestamp bulk writes -         
- Closed
 
-         
- is duplicated by
- 
                    SERVER-40707 Secondary couldn't signal OplogWaiters to advance the lastCommittedOpTime in Chained replication mode -         
- Closed
 
-