[SERVER-81391] Balancer round UID Created: 23/Sep/23 Updated: 12/Dec/23 |
|
| Status: | Needs Scheduling |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Trivial - P5 |
| Reporter: | Renato Riccio | 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: | |||||||||
| Description |
|
Currently there is no simple way to correlate the balancer.round recorded in config.actionlog and the move chunk recorded in config.changelog. Would be great to have a UID per balancer round that will be recorded in both collections config.actionlog and config.changelog. |
| Comments |
| Comment by Adi Zaimi [ 13/Oct/23 ] |
|
FTR, this is related to SERVER-81392. We should consider for the same team to handle both tkts. |
| Comment by Matt Panton [ 06/Oct/23 ] |
|
cris.insignarescuello@mongodb.com - this doesn't fall into the pm-config-server group, but could do accomplished in the small project. I noticed this moved to cluster scalability / sharding nyc. What was driving that change as the related ticket SERVER-81392 did not change backlogs? |