[SERVER-83922] Figure out if we can get rid of GlobalWrite acquisition during sharding initialization Created: 05/Dec/23 Updated: 08/Dec/23 |
|
| Status: | Needs Scheduling |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | sharding-nyc-tech-debt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Cluster Scalability
|
| Participants: |
| Description |
|
We currently take the global lock (example here) during sharding initialization. According to this comment it is only for determining whether it's a primary a secondary, we should be able to do this today with a weaker lock. |