Loading...

XML

Word

Printable

JSON

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

Backwards Compatibility:
Fully Compatible
Sprint:
Storage NYC 2018-12-17, Storage NYC 2018-12-31, Storage NYC 2019-01-14, Storage NYC 2019-01-28, Storage NYC 2019-02-11
Story Points:
20

The index builder interface established is established in ~~SERVER-37636~~.

This ticket will add a Threadpool and move all the instances of MultiIndexBlock (index builder class) that are all over the place behind the interface and running on the Threadpool.

We should be able to register index builds via the interface and then wait upon a condition variable to hear back on the Status result.

Keep in mind ~~SERVER-37644~~, which is to make index builds joinable via the createIndexes command. The condition variable setup must be such that we can have multiple waiters who can all hear back about the same result. Maybe an interface internal helper function to get something to wait upon for a Status result.

causes

SERVER-39368 Refactor IndexBuildsCoordinator::_runIndexBuild

Closed

has to be done after

SERVER-37636 Create an interface through which to act on index builds

Closed

has to be done before

SERVER-37951 Break index builds into phases and add modes

Closed

SERVER-37963 Update metadata command behaviors to either ignore or interrupt index builds

Closed

SERVER-37966 Do not wait for index build completion on startup

Closed

SERVER-39086 Move startup recovery index creation logic into IndexBuildsCoordinator

Closed

SERVER-39314 Update IndexBuildManager unit testing

Closed

is depended on by

SERVER-37940 Establish a code path for FCV 4.0 and FCV 4.2 index builds

Closed

SERVER-39068 Replication of simultaneous index builds startIndexBuild and commitIndexBuild oplog entries

Closed

related to

SERVER-38745 MigrationDestinationManager assigns incorrect timestamps while building multiple indexes

Closed

SERVER-45378 IndexBuildsCoordinator::_setUpIndexBuild() can throw exceptions which should be caught and clean (unregister) the index build

Closed

SERVER-45933 2 phase index build running with maxTimeMS can lead to undesirable behavior like server crash.

Closed

(2 has to be done before, 2 is depended on by, 3 related to)

Assignee:: Benety Goh

Reporter:: Dianna Hohensee (Inactive)

Participants:: Benety Goh, Dianna Hohensee, Githook User

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: Oct 15 2018 08:46:37 PM UTC

Updated:: Oct 29 2023 10:27:20 PM UTC

Resolved:: Feb 01 2019 06:30:14 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates