InterviewSolution
| 1. |
db.sample.deleteOne( { state : "WA" } ) |
|
Answer» In some cases, chunks can grow beyond the specified chunk size but cannot undergo a split. The most COMMON scenario is when a chunk represents a single shard key value. Since the chunk cannot split, it continues to grow beyond the chunk size, becoming a jumbo chunk. These jumbo chunks can become a PERFORMANCE bottleneck as they continue to grow, ESPECIALLY if the shard key value occurs with high frequency. The addition of new data or new shards can result in data distribution imbalances WITHIN the CLUSTER. A particular shard may acquire more chunks than another shard, or the size of a chunk may grow beyond the configured maximum chunk size. MongoDB ensures a balanced cluster using two processes: chunk splitting and the balancer. |
|