Implement an optional serverStatus section, available both on the config server and on the shards, which returns information about all the active chunk migrations. This section will be used by support and possibly by the balancer when it resumes from primary stepdown.
On the shards, this serverStatus section should look like this (and should be placed under the optional sharding section):
sharding: {
migrations: [
{ source: ShardId,
sourceHost: Host:Port,
destination: ShardId,
destinationHost: Host:Port,
chunk: { min: <MinKey>, max: <MaxKey> },
phase: String, one of <INIT, CATCHUP, CRITICAL SECTION>,
},
...
]
}
On the config server, the section should be the union of all migrations across all shards.
- has to be done before
-
SERVER-25334 Add SourceDestinationManager::getMigrationStatusReport to serverStatus (ShardingServerStatus::generateMigrationStatuses)
-
- Closed
-
- related to
-
SERVER-18940 Optimise sharded aggregations that are targeted to a single shard
-
- Closed
-
-
-
- Closed
-