[SERVER-10761] Add a new distributed lock field for "host" Created: 13/Sep/13 Updated: 06/Dec/22 Resolved: 17/Jul/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.5.2 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | remove-distributed-lock-fallout | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Participants: |
| Description |
|
It's currently annoying to have to figure out the current distributed lock host from the process string. |
| Comments |
| Comment by Randolph Tan [ 17/Jul/20 ] |
|
This is no longer relevant as mongos no longer takes distributed locks. |