Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.7.0
Affects Version/s: None
Component/s: Sharding
Labels:
- PM-1645-Milestone-1

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Sharding 2020-05-04
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

Currently, _critSec by itself is not thread safe. All other methods using _critSec takes the CSRLock except for this method.

ShardingMigrationCriticalSection::exitCriticalSection() must lock such that ShardingMigrationCriticalSection::getSignal cannot read the _critSecSignal value while _critSecSignal is being written simultaneously – C++ memory bug.

is depended on by

SERVER-47563 Add concurrency control to the CollectionShardingState class such that it no longer depends upon collection locks for concurrency control

Closed

Assignee:: Randolph Tan
Reporter:: Randolph Tan
Participants:: Dianna Hohensee, Githook User, Kaloian Manassiev, Randolph Tan
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Apr 15 2020 05:48:23 PM UTC
Updated:: Oct 29 2023 10:09:28 PM UTC
Resolved:: Apr 23 2020 06:25:07 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates