[SERVER-2828] Sharding status not communicated across Routers (mongoS) Created: 24/Mar/11 Updated: 12/Jul/16 Resolved: 19/May/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 1.8.0 |
| Fix Version/s: | 1.9.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gaetan Voyer-Perrault | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Repro on 1.8.0. 1. Start sharded set In #2 In #1 ) In #2 === More fun: ); #2 Notice how the indexes were properly communicated? So we somehow communicated the indexes, but not the sharding status. === |
| Comments |
| Comment by auto [ 19/May/11 ] |
|
Author: {u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: fix moveChunk on new mongos |
| Comment by auto [ 19/May/11 ] |
|
Author: {u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: throw StaleConfigException for passthrough command failure with stale config |
| Comment by auto [ 19/May/11 ] |
|
Author: {u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: put all connections that are assigned to ShardConnection into sharded state immediately on creation |
| Comment by Eliot Horowitz (Inactive) [ 06/Apr/11 ] |
|
The correct fix for this is fairly complex, and I dont want to hack it too badly. I added a command to flush the config on a mongos manually With this, after you call shardcollection, you can call that on each mongos, and it'll work around the issus. |
| Comment by David Mytton [ 06/Apr/11 ] |
|
We have new collections created each day and they're automatically sharded. This bug just caused one of our mongos to assert on queries: Wed Apr 6 00:00:53 [WriteBackListener] Assertion: 10181:not sharded:sd.processes_110406 |
| Comment by David Mytton [ 05/Apr/11 ] |
|
+1 for this in 1.8 |
| Comment by Mathias Stearn [ 05/Apr/11 ] |
|
There is a similar issue with settings such as chunksize. There is currently no way to reload them without bouncing a mongos. |
| Comment by auto [ 31/Mar/11 ] |
|
Author: {u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: separate test for |
| Comment by Mathias Stearn [ 30/Mar/11 ] |
|
Not just a display issue (see test) |
| Comment by auto [ 30/Mar/11 ] |
|
Author: {u'login': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: Test for |
| Comment by Eliot Horowitz (Inactive) [ 24/Mar/11 ] |
|
this is just a display issue |