[SERVER-17893] Standalone server to Sharded cluster creates Jumbo chunks Created: 02/Apr/15 Updated: 06/Dec/22 Resolved: 09/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jonathan Abrahams | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | 32qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
In testing a scenario where a large collection is sharded, the collection ends up with too many jumbo chunks, which prevent the chunks from being placed on the proper shard nodes (which are designated using addRangeTag). Schema
Steps
As the chunks are auto-split, most will be marked as jumbo and will not be able to move to their tagged shard. Manual splitting still works on theses chunks. |
| Comments |
| Comment by Jonathan Abrahams [ 07/Apr/15 ] | ||||||||||
|
I reran this scenario without the ShardTagRange as follows:
| ||||||||||
| Comment by Jonathan Abrahams [ 07/Apr/15 ] | ||||||||||
|
The problem is that migrating a replica set to a sharded cluster is creating jumbo chunks, from auto splitting, which can be manually split later. It seems that the mongos should auto split such that jumbo chunks are not created. | ||||||||||
| Comment by Jonathan Abrahams [ 02/Apr/15 ] | ||||||||||
|
A manual split worked using the following commands:
So why would it fail with auto split? |