[SERVER-37202] Abort unprepared transactions holding same Collection lock when entering migration critical section Created: 19/Sep/18 Updated: 27/Oct/23 Resolved: 13/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 4.1.3 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Participants: | |||||||||
| Description |
|
To expedite the acquisition of Collection lock in exclusive mode when entering critical section, the migration should queue a lock request in exclusive mode, abort all unprepared transactions holding the Collection lock and wait for lock request to be granted (prepared transactions should release their resources after they are completed). |
| Comments |
| Comment by Esha Maharishi (Inactive) [ 13/Nov/18 ] |
|
Gone away with design for migration-compatible chunk migration. |