[SERVER-21362] journal sync after applying a batch on pv0 Created: 09/Nov/15 Updated: 28/Sep/16 Resolved: 13/Nov/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.0-rc3 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Milkie | 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, only pv1 does a journal sync after writing the ops to the oplog on secondaries. To simplify behavior with read-concern-level-majority, we should make the journal sync happen for both pv0 and pv1. |
| Comments |
| Comment by Githook User [ 20/Nov/15 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: This reverts commit 9e431f4fd9a6af65292aff3729a3f6d281784ac1. |
| Comment by Matt Dannenberg [ 13/Nov/15 ] |
|
Docs should mention that both PV0 and PV1 journal writes before updating replication progress. |
| Comment by Githook User [ 13/Nov/15 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: |
| Comment by Andy Schwerin [ 10/Nov/15 ] |
|
Alternatively, we could choose not to support majority read concern with replication election protocol 0. |