[SERVER-50968] Uneven distribution of data in sharded cluster Created: 16/Sep/20 Updated: 06/Dec/22 Resolved: 24/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Ankush Sinha | Assignee: | Backlog - Triage Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Triage
|
| Participants: |
| Description |
|
MongoDB Version: 4.2.1 We have a sharded collection where the shard key is {'_id': 'hashed'}and since it has random bytes it should ideally not lead to hot-spotting. The default chunk size has not been changed (default 64MB for the version). We are seeing that the chunks are not evenly distributed among the shards and the majority of data is residing in one shard.
Shard shard7 at shard7/mongo-7:27107,mongo-8:27107,mongo-9:27107 Shard shard1 at shard1/mongo-1:27101,mongo-2:27101,mongo-3:27101 Shard shard6 at shard6/mongo-6:27106,mongo-7:27106,mongo-8:27106 Shard shard5 at shard5/mongo-5:27105,mongo-6:27105,mongo-7:27105 Shard shard9 at shard9/mongo-1:27109,mongo-2:27109,mongo-9:27109 Shard shard8 at shard8/mongo-1:27108,mongo-8:27108,mongo-9:27108 Shard shard2 at shard2/mongo-2:27102,mongo-3:27102,mongo-4:27102 Shard shard3 at shard3/mongo-3:27103,mongo-4:27103,mongo-5:27103 Shard shard4 at shard4/mongo-4:27104,mongo-5:27104,mongo-6:27104 Totals
The result from sh.status(true) can be found here. None of the chunks are marked as Jumbo.
|
| Comments |
| Comment by Dmitry Agranat [ 24/Sep/20 ] |
|
If you need further assistance with shard data distribution, I encourage you to ask our community by posting on the MongoDB Developer Community Forums or on Stack Overflow with the mongodb tag. Regards, |