[SERVER-56779] Do not use the collection distributed lock for chunk merges Created: 08/May/21  Updated: 29/Oct/23  Resolved: 12/Jun/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.2.15, 4.4.7, 4.0.26, 5.0.0-rc2, 5.1.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by SERVER-57032 Acquire only local distLock for Shard... Closed
is depended on by SERVER-56654 Do not use the collection distributed... Closed
Duplicate
is duplicated by SERVER-57115 Merge chunks should wait for any ongo... Closed
is duplicated by SERVER-25359 Create collection-specific ResourceMu... Closed
Problem/Incident
causes SERVER-59929 unexpected slower update/insert opera... Closed
Related
is related to SERVER-56786 There are three routing info refreshe... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0, v4.4, v4.2, v4.0
Sprint: Sharding EMEA 2021-05-17
Participants:
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.



 Comments   
Comment by Githook User [ 24/Jun/21 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-56779 Allow multiple concurrent merges for the same collection across the cluster

(cherry picked from commit e14e6ac61867ebe158fa455f012574ed7e570801)
Branch: v4.0
https://github.com/mongodb/mongo/commit/0e0c905d987713004f273ffb8504e98a988b9fbd

Comment by Githook User [ 24/Jun/21 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-56779 Allow multiple concurrent merges for the same collection across the cluster

(cherry picked from commit d0c6ab09ee3c2726d92b1044577f2c5ebd22b52c)
(cherry picked from commit 3a42f34b634eb9e5b0ccde551f6d8439ed1700c2)
Branch: v4.2
https://github.com/mongodb/mongo/commit/e14e6ac61867ebe158fa455f012574ed7e570801

Comment by Githook User [ 14/Jun/21 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-56779 Allow multiple concurrent merges for the same collection across the cluster

(cherry picked from commit d0c6ab09ee3c2726d92b1044577f2c5ebd22b52c)
Branch: v4.4
https://github.com/mongodb/mongo/commit/3a42f34b634eb9e5b0ccde551f6d8439ed1700c2

Comment by Githook User [ 13/Jun/21 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-56779 Allow multiple concurrent merges for the same collection across the cluster

(cherry picked from commit 792dcddddf6bfedc45208dbc1c513d2dea27546f)
Branch: v5.0
https://github.com/mongodb/mongo/commit/d0c6ab09ee3c2726d92b1044577f2c5ebd22b52c

Comment by Githook User [ 12/Jun/21 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-56779 Allow multiple concurrent merges for the same collection across the cluster
Branch: master
https://github.com/mongodb/mongo/commit/792dcddddf6bfedc45208dbc1c513d2dea27546f

Comment by Githook User [ 03/Jun/21 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: Revert "SERVER-56779 Allow multiple concurrent merges for the same collection across the cluster"

This reverts commit 13e28eb1e3a70211038e10afec3b6713fd63f4b8.
Branch: v5.0
https://github.com/mongodb/mongo/commit/ef8b7e29901be334db20d558972e8a729d8e0d60

Comment by Githook User [ 03/Jun/21 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: Revert "SERVER-56779 Allow multiple concurrent merges for the same collection across the cluster"

This reverts commit 13e28eb1e3a70211038e10afec3b6713fd63f4b8.
Branch: master
https://github.com/mongodb/mongo/commit/dcd9f60e591acffeedabb5fa368f407a035473b2

Comment by Githook User [ 01/Jun/21 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: Revert "SERVER-56779 Allow multiple concurrent merges for the same collection across the cluster"

This reverts commit 6c37e83e56bf2ceea19a4de59a5aba38e28de65a.
Branch: v4.0
https://github.com/mongodb/mongo/commit/5339712ac3d71198ca06fa6894c787010d2d5d96

Comment by Githook User [ 21/May/21 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: Revert "SERVER-56779 Include forgotten file change on the master branch"

This reverts commit 1c4527816ba958d3ec0cd524a1529861b1a7c1c0.

Also reverts "SERVER-56779 Make the sharded_mergeChunks_partitioned.js workload retry on conflicting operations"

This reverts commit 550df92b8967d8845877d409153c349081f5a02e.
Branch: master
https://github.com/mongodb/mongo/commit/eae62a64d0306f761dc110b2148baa4fd1fff126

Comment by Githook User [ 21/May/21 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: Revert "SERVER-56779 Include forgotten file change on the v5.0 branch"

This reverts commit 529d12c821733d0e66ed535a18b53b917f56df4f.
Branch: v5.0
https://github.com/mongodb/mongo/commit/b779af6606bd4133ed29904f8db737872a527832

Comment by Githook User [ 21/May/21 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-56779 Make the sharded_mergeChunks_partitioned.js workload retry on conflicting operations
Branch: master
https://github.com/mongodb/mongo/commit/550df92b8967d8845877d409153c349081f5a02e

Comment by Githook User [ 21/May/21 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-56779 Include forgotten file change on the v5.0 branch
Branch: v5.0
https://github.com/mongodb/mongo/commit/3c8f5c86724afaf73adf8118c0c5564f59cc3f5a

Comment by Githook User [ 20/May/21 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-56779 Include forgotten file change on the master branch
Branch: master
https://github.com/mongodb/mongo/commit/1c4527816ba958d3ec0cd524a1529861b1a7c1c0

Comment by Githook User [ 14/May/21 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-56779 Allow multiple concurrent merges for the same collection across the cluster
Branch: v4.0
https://github.com/mongodb/mongo/commit/6c37e83e56bf2ceea19a4de59a5aba38e28de65a

Comment by Githook User [ 14/May/21 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-56779 Allow multiple concurrent merges for the same collection across the cluster
Branch: master
https://github.com/mongodb/mongo/commit/13e28eb1e3a70211038e10afec3b6713fd63f4b8

Generated at Thu Feb 08 05:40:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.