[SERVER-43457] Complete TODO listed in SERVER-17141 Created: 23/Sep/19  Updated: 29/Oct/23  Resolved: 30/Sep/20

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

Type: Task Priority: Major - P3
Reporter: PM Bot Assignee: Luke Pearson
Resolution: Fixed Votes: 0
Labels: autogen-todo
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-17141 session->truncate failed with File No... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage - Ra 2020-10-05
Participants:
Story Points: 5

 Comments   
Comment by Githook User [ 30/Sep/20 ]

Author:

{'name': 'Luke Pearson', 'email': 'luke.pearson@mongodb.com', 'username': 'luke-pearson'}

Message: SERVER-43457 Removing truncate workaround and related TODO
Branch: master
https://github.com/mongodb/mongo/commit/11eff2c56f44404d3d1ad4c26449507610a0a7e5

Comment by Luke Pearson [ 29/Sep/20 ]

This commit fixed the issue at the time on the WiredTiger side: https://github.com/wiredtiger/wiredtiger/commit/09d345951d43e7ed928980048e5c5c927406a66b#diff-93997252d92d2aa1b01ee68fa0687409

The code that included the fix on the WiredTiger side has since been redone and it isn't clear whether the new code handles the exact scenario in SERVER-17141. As such I can't say definitively whether its a good idea to remove the workaround code, I think it should be okay.

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