[DOCS-14892] Investigate changes in SERVER-59965: Distributed deadlock between renameCollection and multi-shard transaction Created: 25/Oct/21 Updated: 13/Nov/23 Resolved: 23/Feb/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.4, 5.2.0, 5.1.0-rc3, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Dave Cuthbert (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Days since reply: | 1 year, 50 weeks ago | ||||||||||||||||
| Epic Link: | DOCSP-19447 | ||||||||||||||||
| Description |
|
Downstream Change Summary Added new 'metadataRefreshInTransactionMaxWaitBehindCritSecMS' server parameter. Description of Linked TicketAs part of a sharded renameCollection, the DDLCoordinator instructs all participant shards to enter their critical sections. When all shards have entered it, the coordinator will do some work on the configsvr and finally it will tell the shards to leave their critical section. When running renameCollection concurrently with multi-shard transactions that affect that same collection, there exists a particular interleaving that can lead to a distributed deadlock: At this point we are deadlocked:
More generally, I believe this situation can occur in any DDL operation that needs to acquire the critical section in several nodes at the same time. I believe that resharding may also be affected by this. |
| Comments |
| Comment by Githook User [ 23/Feb/22 ] |
|
Author: {'name': 'Dave', 'email': '69165704+davemungo@users.noreply.github.com', 'username': 'davemungo'}Message:
|
| Comment by Githook User [ 23/Feb/22 ] |
|
Author: {'name': 'Dave', 'email': '69165704+davemungo@users.noreply.github.com', 'username': 'davemungo'}Message: |
| Comment by Githook User [ 23/Feb/22 ] |
|
Author: {'name': 'Dave', 'email': '69165704+davemungo@users.noreply.github.com', 'username': 'davemungo'}Message:
|
| Comment by PM Bot [ 25/Oct/21 ] |
|
Downstream changes updated for upstream |