Quick Answer
Jumbo chunks exceed the maximum chunk size (default 128MB) and can't be automatically split or migrated. Caused by: all documents in a chunk share the same shard key value (low cardinality key). The balancer can't rebalance jumbo chunks, causing permanent hotspot on one shard. Fix: choose a higher-cardinality shard key. For existing jumbo chunks, use refineCollectionShardKey or manual splitting.
Answer
Jumbo chunks grow too large to split or migrate, blocking balancing and degrading performance in sharded clusters.
S
SugharaIQ Editorial Team
Verified Answer
This answer has been peer-reviewed by industry experts holding senior engineering roles to ensure technical accuracy and relevance for modern interview standards.
MongoDB interview questions and answers for beginner, junior, mid-level, senior, and expert developers. Perfect for freshers and experienced candidates.