[SERVER-54005] It is possible for the oplogTruncateAfterPoint logic to fail to find a oplog entry w/ timestamp LTE WT's all_durable timestamp Created: 25/Jan/21 Updated: 29/Oct/23 Resolved: 04/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.7, 5.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (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 | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||||||
| Sprint: | Execution Team 2021-05-03, Execution Team 2021-05-17 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 123 | ||||||||||||||||
| Description |
|
It is possible for the oplogTruncateAfterPoint logic to fail to find a oplog entry w/ timestamp LTE WT's all_durable timestamp if the oplog truncation logic manages to delete older oplog entries very quickly. There is nothing stopping this behavior because there currently are no special rules to avoid truncating the oplog needed by the oplogTruncateAfterPoint logic in WiredTigerKVEngine::getPinnedOplog(). |
| Comments |
| Comment by Githook User [ 03/Jun/21 ] |
|
Author: {'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com', 'username': 'DiannaHohensee'}Message: (cherry picked from commit c4065661e5c9c57e8d724243f5f07db72a827090) |
| Comment by Githook User [ 04/May/21 ] |
|
Author: {'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com', 'username': 'DiannaHohensee'}Message: |