[SERVER-18746] ensure WT write-ahead log flush is asynchronous from writes Created: 29/May/15 Updated: 14/Apr/16 Resolved: 23/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Geert Bosch |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | QuInt A (10/12/15) | ||||||||
| Participants: | |||||||||
| Description |
|
Need to hook up new WT journaling feature so that logOp can make use of it on the primary. This way we can allow secondaries to read the oplog without needing to wait for such entries to be journaled first. |