Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.4.18, 3.6.9, 3.7.1, 4.0.0
Affects Version/s: None
Component/s: Index Maintenance, Replication
Labels:
None

Assigned Teams:

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

v3.6, v3.4
Sprint:
Storage 2017-12-04
Case:
Linked BF Score:
0

Currently listIndexes includes in-progress background indexes that haven't been committed yet. This can theoretically (I haven't tested it) lead to an inconsistency in initial sync in the following scenario:

Start bg index on primary
Start initial sync
Initial sync runs listIndexes and builds all returned indexes
Initial sync finishes with the bg index
Kill the bg index build on primary (or have it fail due to a recent insert)

I think after these steps, the secondary will have an index that the primary doesn't.

causes

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

Closed

is depended on by

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

Closed

is duplicated by

SERVER-34970 Consider indicating that an index build is still in progress with .getIndexes()

Closed

related to

SERVER-30224 Need completion flag field in db.coll.getIndexes() output.

Closed

SERVER-37721 Add a command argument to listIndexes to optionally include in-progress index builds

Closed

SERVER-25176 Provide a way to list actively building indexes

Closed

(1 related to)

Assignee:: [DO NOT USE] Backlog - Storage Execution Team

Reporter:: Mathias Stearn

Participants:: [DO NOT USE] Backlog - Storage Execution Team, Githook User, Mathias Stearn

Votes:: 0 Vote for this issue

Watchers:: 15 Start watching this issue

Created:: Jul 20 2016 04:43:17 PM UTC

Updated:: Dec 06 2022 04:21:05 AM UTC

Resolved:: Nov 30 2017 01:11:56 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates