[SERVER-16609] Add ability to configure WT asynchronous logging Created: 19/Dec/14 Updated: 03/Apr/19 Resolved: 12/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage, WiredTiger |
| Affects Version/s: | 2.8.0-rc3 |
| Fix Version/s: | 3.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Asya Kamsky | Assignee: | Geert Bosch |
| Resolution: | Done | Votes: | 1 |
| Labels: | wiredtiger | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Quint 9 09/18/15, QuInt A (10/12/15), QuInt B (11/02/15) | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||
| Description |
|
As of 2.8.0-rc3, WT is not configured to use synchronous logging. That is configured using the WT transaction_sync flag when the engine is opened, or can be controlled on a per-operation basis using the j:true write concern. Currently, the journal is only fsynced when a journal file fills up and rolls over to the next one, or a j:true write is made (it sweeps up all writes before it). There needs to be a knob to control when the journal is fsynced. Makes sense to do this using the existing journalCommitInterval which would trigger a dummy transaction |
| Comments |
| Comment by Githook User [ 13/Oct/15 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert.bosch@mongodb.com'}Message: |
| Comment by Githook User [ 13/Oct/15 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert.bosch@mongodb.com'}Message: |
| Comment by Githook User [ 12/Oct/15 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: |
| Comment by Max Hirschhorn [ 12/Oct/15 ] |
|
Reopening ticket so leaked WiredTigerSession can be fixed. |
| Comment by Githook User [ 11/Oct/15 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert.bosch@mongodb.com'}Message: |
| Comment by Githook User [ 09/Oct/15 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: |
| Comment by Githook User [ 09/Oct/15 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert.bosch@mongodb.com'}Message: |
| Comment by Asya Kamsky [ 03/Feb/15 ] |
|
For 3.0 we should document that WT writes/flushes the journal pretty much "continuously" which is a lot stronger guarantee than mmapv1. I believe this may be part of the reason the delta between journal and no journal metrics is bigger in WT. |