[SERVER-48486] Make WiredTigerCheckpointThread more responsive to syncdelay period changes Created: 29/May/20 Updated: 06/Dec/22 Resolved: 17/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
Currently the WiredTigerCheckpointThread sleeps for 'syncdelay' seconds. If the 'syncdelay' is changed at runtime, the WiredTigerCheckpointThread will continue to use the previous setting until it expires. So, if a user has the default of 60 seconds, then runs the setParameter cmd to change 'syncdelay' to to 5 seconds, the server won't respond to the new value of 5 for 60 seconds. This test does just that, and finishes testing before the checkpoint thread even sees the new 5 value (note, this is a really old test that doesn't matter much). |