Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Gone away
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Storage
Labels:
- rollback-optional

Backwards Compatibility:
Fully Compatible
Sprint:
Repl 2017-12-18, Repl 2018-01-01, Repl 2018-01-15
Confidence Status:
None
Work Order:
3

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

When running verifyTable on a WiredTiger file that is not clean, it forces a checkpoint. As we need to avoid creating a checkpoint with data that is not majority confirmed, this behavior is problematic.

Instead, have full validate first take a MODE_S lock on the collection and then call a new method on the WiredTigerCheckpointThread that will trigger and wait for a new majority-confirmed checkpoint.

depends on

SERVER-29891 Roll Back to Checkpoint: Call setStableTimestamp() when commit point or last applied changes

Closed

SERVER-29212 Ensure WiredTiger checkpoints are created at valid timestamps

Closed

WT-3387 Add support for a stable timestamp

Closed

is duplicated by

SERVER-30817 Make full validate block until a new majority-confirmed checkpoint is created

Closed

Assignee:: Daniel Gottlieb (Inactive)
Reporter:: Geert Bosch
Participants:: Daniel Gottlieb, Geert Bosch, Ian Whalen
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: Jun 07 2017 03:58:54 PM UTC
Updated:: Oct 27 2023 08:44:04 PM UTC
Resolved:: Jan 09 2018 06:28:43 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates