[SERVER-32533] In oplog truncate with WT, don't use a start key Created: 03/Jan/18  Updated: 30/Oct/23  Resolved: 23/Jan/18

Status: Closed
Project: Core Server
Component/s: Storage, WiredTiger
Affects Version/s: None
Fix Version/s: 3.4.14, 3.6.3, 3.7.2

Type: Bug Priority: Major - P3
Reporter: Judah Schvimer Assignee: Michael Cahill (Inactive)
Resolution: Fixed Votes: 0
Labels: RF
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File repro_server32533-fixed.patch     Text File repro_server32533.patch    
Issue Links:
Backports
Duplicate
is duplicated by SERVER-31924 OplogStones can capture record ids to... Closed
Problem/Incident
causes WT-3946 Truncate segfault with a NULL start c... Closed
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.6, v3.4
Sprint: Storage 2018-01-15, Storage 2018-01-29
Participants:
Linked BF Score: 0

 Description   

A user experienced a case where oplog entries were unexpectedly found at the beginning of the oplog after later records were truncated.



 Comments   
Comment by Githook User [ 26/Feb/18 ]

Author:

{'email': 'michael.cahill@mongodb.com', 'name': 'Michael Cahill', 'username': 'michaelcahill'}

Message: SERVER-32533 In oplog truncate with WT, don't use a start key.

Previously there was a performance benefit to tracking the first
expected key in the oplog. The performance issue is no longer
relevant, and supplying a key makes the code fragile (if the tracked
key gets out of sync with the real first key).

(cherry picked from commit f4ac177b55bc762e977dc093a40e442b7061f58c)
Branch: v3.4
https://github.com/mongodb/mongo/commit/35582b7fadbab50130afed7044dc89ab655bae7b

Comment by Githook User [ 23/Jan/18 ]

Author:

{'name': 'Michael Cahill', 'email': 'michael.cahill@mongodb.com', 'username': 'michaelcahill'}

Message: SERVER-32533 In oplog truncate with WT, don't use a start key.

Previously there was a performance benefit to tracking the first
expected key in the oplog. The performance issue is no longer
relevant, and supplying a key makes the code fragile (if the tracked
key gets out of sync with the real first key).

(cherry picked from commit f4ac177b55bc762e977dc093a40e442b7061f58c)
Branch: v3.6
https://github.com/mongodb/mongo/commit/397963a23343862d49c5c76c42f031e86b43407d

Comment by Githook User [ 23/Jan/18 ]

Author:

{'name': 'Michael Cahill', 'email': 'michael.cahill@mongodb.com', 'username': 'michaelcahill'}

Message: SERVER-32533 In oplog truncate with WT, don't use a start key.

Previously there was a performance benefit to tracking the first
expected key in the oplog. The performance issue is no longer
relevant, and supplying a key makes the code fragile (if the tracked
key gets out of sync with the real first key).
Branch: master
https://github.com/mongodb/mongo/commit/f4ac177b55bc762e977dc093a40e442b7061f58c

Comment by Judah Schvimer [ 03/Jan/18 ]

SERVER-31924 may be the same bug, though daniel.gottlieb does not think so. The solution proposed in SERVER-31924 may fix this as well.

Generated at Thu Feb 08 04:30:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.