Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.7.0
Affects Version/s: None
Component/s: None
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Execution Team 2020-08-10, Execution Team 2020-08-24, Execution Team 2020-09-07

After ~~SERVER-50168~~, this work should simply entail enabling rollback_resumable_index_build_collection_scan_phase.js.

Original description:

If a node goes into rollback during the collection scan of a resumable index build, the majority committed view gets zeroed out which causes the scan to throw ReadConcernMajorityNotAvailableYet. We then hit this invariant since we currently do not expect an index build to fail this way.

depends on

SERVER-50168 Transition to rollback doesn't need to clear out the majority committed snapshot's timestamp.

Closed

is related to

SERVER-48418 Rollback restart resumable index builds from beginning

Closed

SERVER-48476 resumable index build should use majority read cursor for collection scan

Closed

related to

SERVER-49075 Add replica_sets suite to resumable index build variant

Closed

SERVER-49076 Add rollback fuzzer suites to resumable index build variant

Closed

Assignee:: Gregory Noma

Reporter:: Gregory Noma

Participants:: Benety Goh, Githook User, Gregory Noma, Suganthi Mani

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Created:: Jul 21 2020 06:19:20 PM UTC

Updated:: Oct 29 2023 10:05:28 PM UTC

Resolved:: Sep 02 2020 09:39:53 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates