[SERVER-28841] CollectionShardingState / ScopedCollectionMetadata destructor races - MongoDB Jira

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Major - P3
Resolution: Fixed
Affects Version/s: 3.4.0, 3.5.7
Fix Version/s: 3.4.5, 3.5.8
Component/s: Sharding
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Steps To Reproduce:

Hide

Intermittent; run jstests

Show
Intermittent; run jstests
Sprint:
Sharding 2017-05-29
Linked BF Score:
0

Description

There are numerous races of various sorts around destruction of MetadataManager and ScopedCollectionMetadata objects. Fixing them requires changes to ScopedCollectionMetadata and CollectionMetadataTracker layout, and locking in the MetadataManager destructor.

Reproduce by running jstests/sharding/cleanup_orphaned_cmd_during_movechunk.js and jstests/concurrency/fsm_all_simultaneous repeatedly.

Attachments

Activity

People

Assignee:: Nathan Myers

Reporter:: Nathan Myers

Participants:: Githook User, Nathan Myers

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: Apr 18 2017 03:45:00 PM UTC

Updated:: Oct 12 2017 08:59:34 PM UTC

Resolved:: May 16 2017 08:56:30 PM UTC