[SERVER-34018] Stashed transaction resources for snapshot reads can block the migration critical section, leading to stalls Created: 20/Mar/18  Updated: 06/Dec/22  Resolved: 25/Jan/19

Status: Closed
Project: Core Server
Component/s: Replication, Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-38147 Cap donor migration lock acquisition ... Closed
Assigned Teams:
Sharding
Participants:

 Comments   
Comment by Kaloian Manassiev [ 21/Mar/18 ]

Putting this to be considered as part of the planning for GPiTR for the next 2 iterations.

Comment by Tess Avitabile (Inactive) [ 20/Mar/18 ]

They can also block on the destination shard any time we take a MODE_X lock during migration. For example, we take a MODE_X lock on the database when we check if the collection exists.

Generated at Thu Feb 08 04:35:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.