Loading...

XML

Word

Printable

JSON

Details

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.0.0-rc6, 4.1.1
Affects Version/s: None
Component/s: Replication
Labels:
None

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

v4.0
Sprint:
Repl 2018-06-04, Repl 2018-06-18
Linked BF Score:
65

Description

One problem we've noted is that this call to mark collections as needing size adjustment is not gated on being in storage recovery, which is what it's meant for. This means any collections that are created are marked as needing size adjustment, even if later writes would ensure they have a non-zero size at the stable timestamp when we enter rollback. To fix this, we can clear the "needing size adjustment" set at the beginning of replication rollback.

Attachments

Issue Links

is related to

SERVER-33488 WT SizeStorer dislikes RTT

Closed

SERVER-33863 Add transactions and ddl operations on transactions table to rollback fuzzer

Closed

related to

SERVER-34977 subtract capped deletes from fastcount during replication recovery

Closed

SERVER-35435 Renaming during replication recovery incorrectly allows size adjustments

Closed

SERVER-42312 Validate during rollback can cause count mismatch

Closed

SERVER-35052 Turn off fastcount checks on capped collections in rollback fuzzer

Closed

(1 related to)

Activity

People

Assignee:: Judah Schvimer

Reporter:: Judah Schvimer

Participants:: Githook User, Judah Schvimer, Siyuan Zhou

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: May 14 2018 01:42:49 PM UTC

Updated:: Oct 29 2023 10:31:51 PM UTC

Resolved:: Jun 12 2018 06:18:54 PM UTC