Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.4.14, 3.6.3, 3.7.2
Affects Version/s: None
Component/s: Storage, WiredTiger
Labels:
- RF

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v3.6, v3.4
Sprint:
Storage 2018-01-15, Storage 2018-01-29
Linked BF Score:
0
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List
  - Download All

repro_server32533.patch
8 kB
Jan 09 2018 12:19:36 PM UTC
repro_server32533-fixed.patch
8 kB
Jan 10 2018 05:37:34 AM UTC

causes

WT-3946 Truncate segfault with a NULL start cursor

Closed

is duplicated by

SERVER-31924 OplogStones can capture record ids to truncate out of order

Closed

Assignee:: Michael Cahill (Inactive)
Reporter:: Judah Schvimer
Participants:: Githook User, Judah Schvimer, Michael Cahill
Votes:: 0 Vote for this issue
Watchers:: 27 Start watching this issue

Created:: Jan 03 2018 08:02:17 PM UTC
Updated:: Oct 30 2023 11:09:35 PM UTC
Resolved:: Jan 23 2018 06:05:49 AM UTC
Confidence Status Last Update:: 10/Jan/18 10:14 PM