[SERVER-9194] Reduce the lock take over time Created: 01/Apr/13 Updated: 06/Dec/22 Resolved: 21/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Alberto Lerner | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Participants: |
| Description |
|
This work involves converting the semantics of the distributed lock more into a lease. We'd like, for instance, to assert if the lock is held based on the lock pinger. For another instance, we'd like to be able to issue an applyOps mentioning under which lock it protected – and have the config servers check that lock. |