-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
-
Fully Compatible
-
Sharding EMEA 2022-03-07, Sharding EMEA 2022-03-21
Currently, all MigrateInfos have a MigrationReason. However, the migration reasons are only used for returning the first compliance violation in the balancer status command. Instead of storing a MigrationReason for each MigrateInfo, we should return only the first violation reason separate from the MigrateInfoVector while running selectChunksToMove.
- causes
-
SERVER-64512 Coverity analysis defect 121880: Parse warning
- Closed