Loading...

XML

Word

Printable

JSON

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

Backwards Compatibility:
Fully Compatible
Sprint:
Storage NYC 2018-03-26, Storage NYC 2018-04-09, Storage NYC 2018-04-23
Linked BF Score:
63
Confidence Status:
None
Work Order:
3

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

The fuzzer uncovered an issue where the database was locked in global exclusive mode while the catalog was being modified. A concurrent thread performed UUID to namespace resolution, trying to query a collection, and got a NamespaceNotFound error because the UUID catalog was transiently empty. This situation should not have been observable because of the global exclusive lock.

is related to

SERVER-29839 Protect against UUID->NSS mapping changing after looking it up in all commands that use parseNsOrUUID

Closed

SERVER-34615 find by UUID can return NamespaceNotFound for a collection that is concurrently renamed

Closed

SERVER-33474 Blacklist restart_catalog.js from suites involving initial sync

Closed

related to

SERVER-32367 AutoGetCollectionOrView and its related classes perform shard version checking on a view

Closed

SERVER-69389 Command checkAuthorization may throw ErrorCodes::NamespaceNotFound for existing collection while trying to resolve UUID to namespace when the node is shutting down.

Closed

Assignee:: Geert Bosch
Reporter:: Gregory McKeon (Inactive)
Participants:: Geert Bosch, Githook User, Gregory McKeon, Judah Schvimer, Kaloian Manassiev, Louis Williams, Spencer Brody
Votes:: 0 Vote for this issue
Watchers:: 9 Start watching this issue

Created:: Mar 02 2018 07:33:38 PM UTC
Updated:: Oct 29 2023 10:34:12 PM UTC
Resolved:: Apr 17 2018 09:39:18 PM UTC
Confidence Status Last Update:: 26/Mar/18 2:15 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates