Loading...

XML

Word

Printable

JSON

Details

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.2.15, 4.4.7, 4.0.26, 5.0.0-rc2, 5.1.0-rc0
Affects Version/s: None
Component/s: Sharding
Labels:
- sharding-wfbf-day

Backwards Compatibility:
Fully Compatible
Backport Requested:

v5.0, v4.4, v4.2, v4.0
Sprint:
Sharding EMEA 2021-05-17
Case:

Description

Currently chunk merges acquire the collection distributed lock. This means that it is not possible to run more than one merge at a time for the entire cluster or if there are any ongoing splits or balancing (again for the entire cluster).

This ticket is to figure out how to remove the dist lock acquisition from merges without causing the much more expensive moves to start failing, because the chunk being moved got merged.

Attachments

Issue Links

causes

SERVER-59929 unexpected slower update/insert operation bease of splitchunk and moveChunk

Closed

is depended on by

SERVER-57032 Acquire only local distLock for Sharding DDL coordinators

Closed

SERVER-56654 Do not use the collection distributed lock for chunk splits

Closed

is duplicated by

SERVER-57115 Merge chunks should wait for any ongoing moves to complete

Closed

SERVER-25359 Create collection-specific ResourceMutex map to allow split/merge/move chunk on different collections to proceed in parallel

Closed

is related to

SERVER-56786 There are three routing info refreshes and two chunk scans on the mergeChunks path

Closed

(1 is related to)

Activity

People

Assignee:: Kaloian Manassiev

Reporter:: Kaloian Manassiev

Participants:: Githook User, Kaloian Manassiev

Votes:: 0 Vote for this issue

Watchers:: 9 Start watching this issue

Dates

Created:: May 08 2021 05:14:20 AM UTC

Updated:: Oct 29 2023 09:53:51 PM UTC

Resolved:: Jun 12 2021 08:21:33 PM UTC