Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.0.2, 4.1.2
Affects Version/s: None
Component/s: Sharding
Labels:
None

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

v4.0
Sprint:
Sharding 2018-08-13
Linked BF Score:
17
Confidence Status:
None
Work Order:
3

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

NamespaceSerializer was added to createCollection to prevent unneeded timeouts occurring when several create operations in parallel try to acquire the same distributed lock. The same should be applied to dropCollection.

is duplicated by

SERVER-31643 Make drop collection in concurrency workloads retry LockBusy errors

Closed

is related to

SERVER-36433 NamespaceSerializer lock should be used during drop database

Closed

related to

SERVER-47422 Use NamespaceSerializer when taking distributed locks for refineCollectionShardKey and migrations

Closed

SERVER-49145 Prevent distributed lock timeouts in suites with background migrations

Closed

Assignee:: Janna Golden
Reporter:: Matthew Saltz (Inactive)
Participants:: Githook User, Janna Golden, Matthew Saltz
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Jul 27 2018 03:14:08 PM UTC
Updated:: Oct 29 2023 10:29:29 PM UTC
Resolved:: Aug 03 2018 08:50:32 PM UTC
Confidence Status Last Update:: 03/Aug/18 3:57 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates