[SERVER-30827] Provide new interface for getting new OpTimes for vector insert from the optime generator Created: 25/Aug/17 Updated: 30/Oct/23 Resolved: 22/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Eric Milkie |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Backport Requested: |
v3.4
|
||||||||||||||||||||
| Sprint: | Storage 2017-09-11 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Currently, the optime generator is only accessed via logOp() and logInsertOps() called via an opObserver. One such need is for transactions that write multiple oplog entries, such as vectored insert. |
| Comments |
| Comment by Eric Sedor [ 22/Apr/19 ] |
|
This ticket fixed the issue described in If it is straightforward to backport this fix to 3.4, that would help mitigate write latency spikes on sharded clusters when a Secondary config server is chaining during a blocking cache update, as is observed in |
| Comment by Ramon Fernandez Marina [ 12/Sep/17 ] |
|
Author: {'username': u'milkie', 'name': u'Eric Milkie', 'email': u'milkie@10gen.com'}Message: |
| Comment by Ian Whalen (Inactive) [ 01/Sep/17 ] |
|
Superseded by |
| Comment by Eric Milkie [ 25/Aug/17 ] |
|
Proposal is to reduce the number of parameters to logOp() as part of this work. |