[SERVER-17852] Reduce unnecessary replicated journal write concern flag for multi-update/delete Created: 01/Apr/15 Updated: 14/Apr/16 Resolved: 29/Apr/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Siyuan Zhou | Assignee: | Siyuan Zhou |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Description |
|
In implementing |
| Comments |
| Comment by Scott Hernandez (Inactive) [ 01/Apr/15 ] |
|
One possible implementation would be to introduce a new write concern operation type for replication to enforce the journal write at the end of the multi-operation or write command batch, instead of using the current "j" flag on an oplog entry. This would allow us to be more precise with placing the "journal" event in the sequence of writes which are replicated, via the oplog. |