[SERVER-64149] Remove MigrationReason from MigrateInfo Created: 03/Mar/22  Updated: 29/Oct/23  Resolved: 15/Mar/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Allison Easton Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
causes SERVER-64512 Coverity analysis defect 121880: Pars... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-03-07, Sharding EMEA 2022-03-21
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 15/Mar/22 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-64149 Remove MigrationReason from MigrateInfo
Branch: master
https://github.com/mongodb/mongo/commit/39ecdd92807aafc5c75dc1ad2bffad88f293d294

Generated at Thu Feb 08 05:59:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.