[SERVER-3842] Multiple mongos can interfere in initial sharding Created: 14/Sep/11 Updated: 11/Jul/16 Resolved: 22/Oct/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 2.0.2, 2.1.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 3 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
The initial chunk split of a newly sharded collection can be interrupted by an autosplit, particularly if the collection is large and the calculation of many split points is slow. Fix should be to calc (and potentially split) the chunk before creating the sharded collection entry in the config server to prevent other mongoses from detecting the sharded collection. |
| Comments |
| Comment by auto [ 24/Oct/11 ] |
|
Author: {u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: |
| Comment by auto [ 22/Oct/11 ] |
|
Author: {u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: |
| Comment by Eliot Horowitz (Inactive) [ 30/Sep/11 ] |
|
You should just check your mongos logs for errors and check that the # of chunks (via db.printShardingStatus()) is approximately correct |
| Comment by m [ 30/Sep/11 ] |
|
I'm running a 2.0.0 standard replica set with some large collections and will be sharding it this weekend. Can you please elaborate on this issue, including precautions and advice/workarounds for making this as smooth as possible. Current config: Hopeful config: |