Description
The docs could be clearer when handling the phrase "jumbo chunks". This is used interchangably to refer to each of:
- chunk that has been marked with the jumbo: true flag
- chunk that is indivisible, and will be marked as jumbo: true if the balancer attempts to move it (but currently doesn't have jumbo: true)
- chunk that is divisible, but has been marked as jumbo: true for some other reason (eg.
SERVER-19919, SERVER-21931).
- chunk that is informally very large and difficult to migrate or work with (but may in fact be divisible)
I'm not sure if #3 and #4 are actually a problem in the docs — it might be more in discussions elsewhere about jumbo chunks.
In any case, the docs would benefit from some discussion around "jumbo as in jumbo: true" vs "jumbo as in indivisible and large".
Examples:
Scope of changes
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
|