[SERVER-39719] Ensure that a node performing an initial sync from a secondary with a in-progress index build creates the index before initial sync is done - MongoDB Jira

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Major - P3
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 4.0.7, 4.1.9
Component/s: Storage
Labels:
None

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

v4.0
Sprint:
Storage NYC 2019-02-25, Storage NYC 2019-03-11

Description

This issue arose from the work done in ~~SERVER-25175~~.
A secondary node that is initial syncing from another secondary node with an in-progress index build, will not build the in-progress index build during the initial sync phase. It will only build the finished indexes from the secondary node that it is initial syncing from.

The work for this ticket is to write a test to showcase the correct behaviour. We will need to revert the work done in ~~SERVER-25175~~ to make the test work.

Attachments

Issue Links

depends on

SERVER-25175 listIndexes shouldn't include in-progress background index builds on primary nodes

Closed

SERVER-39787 Add buildUUID as an allowed index spec field name

Closed

SERVER-39723 Change listIndexes command behavior to show in-progress index builds

Closed

Activity

People

Assignee:: Gregory Wlodarek

Reporter:: Gregory Wlodarek

Participants:: Githook User, Gregory Wlodarek

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: Feb 21 2019 04:47:10 PM UTC

Updated:: Feb 27 2019 01:54:47 AM UTC

Resolved:: Feb 27 2019 01:54:47 AM UTC