[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: |
|
||||||||
| 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. |