[SERVER-45721] Make truncation using oplogTruncateAfterPoint always non-inclusive of the oplogTruncateAfterPoint Created: 23/Jan/20  Updated: 29/Oct/23  Resolved: 29/Jan/20

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.3.4

Type: Task 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:
Depends
Problem/Incident
Related
is related to SERVER-46065 backup_cursor_truncate_after.js shoul... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-01-27, Execution Team 2020-02-10
Participants:
Linked BF Score: 35

 Comments   
Comment by Githook User [ 29/Jan/20 ]

Author:

{'username': 'DiannaHohensee', 'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com'}

Message: SERVER-45721 truncation using the oplogTruncateAfterPoint is always non-inclusive of the oplogTruncateAfterPoint
Branch: master
https://github.com/mongodb/mongo/commit/7442016d9fd45928370084da1899bc63240a3486

Comment by Githook User [ 29/Jan/20 ]

Author:

{'name': 'Dianna Hohensee', 'username': 'DiannaHohensee', 'email': 'dianna.hohensee@mongodb.com'}

Message: SERVER-45721 truncation using the oplogTruncateAfterPoint is always non-inclusive of the oplogTruncateAfterPoint
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/4ef3662babc9b84838c1ba9d796284f7c037af1d

Generated at Thu Feb 08 05:09:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.