-
Type:
New Feature
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
Catalog and Routing
Currently, if the balancer goes to split a chunk and cannot, the chunk gets marked as 'jumbo', which will prevent the balancer from migrating that chunk and from trying to split it again.
If in the future, documents are deleted from that shard key range or the cluster's chunksize setting changes, the chunk itself may no longer be 'jumbo', but MongoDB will not clear the 'jumbo' flag from that chunk.
If you have a system where documents are short-lived (say, one week) and are then removed from the system, this will result in a system with a large number of chunks that are incorrectly marked 'jumbo'. In addition, the number of 'jumbo' chunks will grow over time.
- depends on
-
SERVER-86055 Automatically clear jumbo flags before shard removal
-
- Backlog
-
- is duplicated by
-
SERVER-36059 Can't move jumbo chunks even after changing chunk size
-
- Closed
-
- is related to
-
SERVER-13806 Need better detection and reporting of the existence of jumbo chunks
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Backlog
-
- related to
-
-
- Closed
-
-
-
- Closed
-