Currently, if removeShard is called while the shard is still draining the output of the command is
{
msg: "draining ongoing",
state: "ongoing",
remaining: chunks:5, dbs:1,
note:"you need to drop or movePrimary these databases dbsToMove"
}
The only place the number of jumbo chunks that remains is reported is in the config server logs. It would be more helpful if we also reported this number in the command output as well. We do a find on config.chunks in order to report the number of chunks remaining, so it should be easy to search for those entries which have 'jumbo: true'.
- is documented by
-
DOCS-13246 Investigate changes in SERVER-44476: Include number of jumbo chunks remaining in output of removeShard
-
- Closed
-
- related to
-
SERVER-42273 Introduce a "force" option to `moveChunk` to allow migrating jumbo chunks
-
- Closed
-