[SERVER-62968] RSM Topology Change message log publishes redundant information Created: 25/Jan/22 Updated: 12/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.3.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Rachita Dhawan | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | neweng, sharding-nyc-subteam2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Assigned Teams: |
Cluster Scalability
|
| Operating System: | ALL |
| Participants: | |
| Story Points: | 1 |
| Description |
|
Currently, the message logs the same information(replicaSet Name) under the keys - "replicaSet" and "setName". And most of the RSM subsystem uses "replicaSet" for the same information. We should update the message logging to remove "setName".
|