[SERVER-21129] Allow pipelining of applier work before updating-position/reporting Created: 26/Oct/15 Updated: 10/Mar/16 Resolved: 30/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.0-rc2 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Matt Dannenberg |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | Repl C (11/20/15) | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Currently the applier must (sequentially) do the following in a loop:
The task here is to break the last two steps (journal + reporting) into a separate process which doesn't block the next batch from starting/applying. This should allow higher throughput on the replicas without adversely affecting latency. |
| Comments |
| Comment by Githook User [ 30/Oct/15 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: |
| Comment by Scott Hernandez (Inactive) [ 26/Oct/15 ] |
|
Matt, let's talk in the morning so we can get a spike done asap. |