[SERVER-26285] ShardCollection on existing collection can sometimes fail to create more than 1 chunk Created: 23/Sep/16 Updated: 25/Jan/17 Resolved: 04/Oct/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2016-10-10 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
It looks like there are some cases when splitVector is not called on the shard and shardCollection ends up just creating a single chunk for a huge collection. |
| Comments |
| Comment by Githook User [ 04/Oct/16 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: |
| Comment by Githook User [ 04/Oct/16 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: |
| Comment by Randolph Tan [ 29/Sep/16 ] |
|
Looks like the balancer configuration is currently only refreshed during startup and when the autosplit threshold is triggered. It means that there is a potential race between changing the setting in the config server document and the mongos reading the setting with the latest changes immediately after. |