Loading...

XML

Word

Printable

JSON

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

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Execution Team 2020-07-27
Linked BF Score:
6
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

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

When a mongod restarts and attempts to rebuild its unfinished indexes, it does so before the FCV version has been initialized. When the in-progress index specs are validated, therefore, the index comparison defaults to the FCV 4.4 behaviour and does not distinguish the indexes based on their differing partialFilterExpressions. This will cause an fassert if any conflicting indexes exist.

Similar issues have occurred before; see e.g. ~~SERVER-45374~~. After speaking with louis.williams and daniel.gottlieb, the consensus is that the proper solution would be to ensure that the FCV is always initialized before attempting any index validation.

has to be done before

SERVER-49301 remove startingAfterUncleanShutdown decorator

Closed

is related to

SERVER-49775 Fix uninitialized FCV check when starting up with resumable index builds enabled

Closed

SERVER-50139 Skip level upgrade with --repair leaves repair in incomplete state

Closed

related to

SERVER-48044 FCV::isVersion should invariant if FCV is unset

Closed

SERVER-106123 Evaluate lock mode for fetching the FCV document

Closed

Assignee:: Louis Williams
Reporter:: Bernard Gorman
Participants:: Bernard Gorman, Githook User, Louis Williams, Siyuan Zhou
Votes:: 0 Vote for this issue
Watchers:: 8 Start watching this issue

Created:: May 08 2020 05:03:39 PM UTC
Updated:: Jun 16 2025 05:53:51 PM UTC
Resolved:: Jul 20 2020 05:59:24 PM UTC
Confidence Status Last Update:: 13/Jul/20 2:28 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates