[SERVER-81442] Poke WT oplog reclamation thread periodically Created: 26/Sep/23 Updated: 30/Nov/23 Resolved: 14/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0, 7.0.5, 6.0.13, 5.0.24 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dan Larkin-York | Assignee: | Daotang Yang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v7.0, v6.0, v5.0
|
||||||||
| Sprint: | Execution Team 2023-11-13, Execution Team 2023-11-27 | ||||||||
| Participants: | |||||||||
| Description |
|
Currently we only perform checks (in the oplog reclamation thread) as to whether the WT oplog can be truncated when a) we finish sampling the oplog during recovery, b) we resize the oplog, or c) we create a new oplog stone. In cases where the oplog size exceeds the limit, but the oplog window is smaller than the configured retention period, we may (correctly) choose not to truncate the oplog at a given point in time. However, if enough time passes so that the oplog window grows, but one of the three triggering events described above does not occur, we currently will not truncate the oplog. For instance, during a long period of low write activity, we may not generate a new oplog stone, leaving the oplog untruncated for a long period of time. |
| Comments |
| Comment by Githook User [ 30/Nov/23 ] |
|
Author: {'name': 'Daotang Yang', 'email': 'daotang.yang@mongodb.com', 'username': ''}Message: (cherry picked from commit 068fc443154eee243bb24802f96baa5a4d370ddd) |
| Comment by Githook User [ 29/Nov/23 ] |
|
Author: {'name': 'Daotang Yang', 'email': 'daotang.yang@mongodb.com', 'username': ''}Message: (cherry picked from commit 068fc443154eee243bb24802f96baa5a4d370ddd) |
| Comment by Githook User [ 29/Nov/23 ] |
|
Author: {'name': 'Daotang Yang', 'email': 'daotang.yang@mongodb.com', 'username': ''}Message: (cherry picked from commit 068fc443154eee243bb24802f96baa5a4d370ddd) |
| Comment by Githook User [ 14/Nov/23 ] |
|
Author: {'name': 'Daotang Yang', 'email': 'daotang.yang@mongodb.com', 'username': ''}Message: |