[SERVER-29210] Create a thread in MongoDB to manage WiredTiger checkpoints Created: 15/May/17 Updated: 30/Oct/23 Resolved: 01/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.9 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Alexander Gorrod | Assignee: | Daniel Gottlieb (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | Storage 2017-05-29, Storage 2017-06-19 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
At the moment MongoDB utilises a utility thread inside WiredTiger to create checkpoints. The thread is configured with: The goal of this work is to stop using the WiredTiger managed checkpoint thread, and instead manage checkpoint creation in MongoDB. The work needs to consider:
|
| Comments |
| Comment by Githook User [ 01/Jun/17 ] |
|
Author: {u'username': u'dgottlieb', u'name': u'Daniel Gottlieb', u'email': u'daniel.gottlieb@10gen.com'}Message: Prior to this change, WiredTiger would be started with a configuration that The checkpoint thread now only checkpoints every 60 seconds (still |
| Comment by Susan LoVerso [ 18/May/17 ] |
|
It will not be easy to measure the volume of data written to the WT log files. It could be approximated with a log cursor setting a cursor key to the first record of a log file and calling search to see if the record is found or not, knowing about how much data ends up in a log file and multiplying out. However, we should be logging a lot less anyway so that rate would have to be scaled back if used. Another (cleaner IMO) way to get a more accurate measurement would be to use a statistics cursor and look at the log bytes written periodically. |