[SERVER-46853] OperationContext API should have way to request being killed on stepdown even if a global lock has not been taken Created: 13/Mar/20 Updated: 06/Dec/22 Resolved: 01/Nov/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (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: | |||||||||||||
| Description |
|
Right now, sharding has been working around this issue by acquiring and immediately releasing a global IX lock, see example here. Assigning to the sharding backlog for now, but it might make sense to be owned by Service Architecture or Replication. |