[SERVER-63592] Investigate how a sharded cluster can end up with config.system.sessions collection with different uuids Created: 11/Feb/22 Updated: 12/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Sharding |
| 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: | cs-subteam1, sharding-nyc-subteam1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Cluster Scalability
|
||||||||
| Participants: | |||||||||
| Comments |
| Comment by Randolph Tan [ 11/Feb/22 ] |
|
In the linked ticket, one of the user observed this in v4.0.27 and another one observed this after upgrading from v4.0.23 to v4.2.14. |