[SERVER-4399] mongos doesn't always update shards in response to replica set changes Created: 30/Nov/11 Updated: 11/Jul/16 Resolved: 12/Dec/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.0.2, 2.1.0 |
| Fix Version/s: | 2.0.3, 2.1.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
when adding or removing a member from a replica set via a reconfig, mongos does not always update the config.shards collection. Seems to update on startup, but not on general reconfig. |
| Comments |
| Comment by auto [ 01/Feb/12 ] |
|
Author: {u'login': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |
| Comment by auto [ 09/Dec/11 ] |
|
Author: {u'login': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |
| Comment by auto [ 09/Dec/11 ] |
|
Author: {u'login': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |
| Comment by Greg Studer [ 01/Dec/11 ] |
|
Don't think it's a regression, but do think it's an oversight - we never update replica sets on node removal (not sure there is a way to remove an old node aside from restarting mongos?) Patch is mostly done, can test once buildbot is sane again. |
| Comment by Greg Studer [ 30/Nov/11 ] |
|
Not sure if it's a regression from 1.8/2.0.1 |