Details
-
New Feature
-
Status: Needs Scheduling
-
Major - P3
-
Resolution: Unresolved
-
None
-
None
-
None
-
Sharding EMEA
Description
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.
Attachments
Issue Links
- is duplicated by
-
SERVER-36059 Can't move jumbo chunks even after changing chunk size
-
- Closed
-
- is related to
-
DOCS-5701 Jumbo chunks are never cleared automatically
-
- Closed
-
-
SERVER-13806 Need better detection and reporting of the existence of jumbo chunks
-
- Closed
-
-
SERVER-21931 Only mark chunks as jumbo if split fails because the chunk is too large
-
- Closed
-
-
SERVER-40435 A clearJumboChunk command to clear the jumbo flag
-
- Closed
-
- related to
-
SERVER-11629 Allow Jumbo Chunks to be Drained / Migrated
-
- Closed
-
-
SERVER-14121 Store size for chunk in config.chunks.
-
- Closed
-
-
DOCS-4163 Document how to manually reset Jumbo flag on chunks
-
- Closed
-