[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: File mongos_no_replica_set_refresh.js    
Issue Links:
Depends
Duplicate
is duplicated by SERVER-4453 Shards not picking up replica set upd... Closed
Related
related to SERVER-7278 mongos doesn't always update shards i... Closed
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.
Test case reproduces.



 Comments   
Comment by auto [ 01/Feb/12 ]

Author:

{u'login': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-4399 make replica set updating more reliable in c++ driver, remove nodes when no longer present in config
Branch: v2.0
https://github.com/mongodb/mongo/commit/6b2231a15c45104c5e8ed292ab4eb5ad3fc94a29

Comment by auto [ 09/Dec/11 ]

Author:

{u'login': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-4399 test case to ensure mongos updates config server with new rs data
Branch: master
https://github.com/mongodb/mongo/commit/b064cb5acb35db617250703e5da2cfbb4a939f01

Comment by auto [ 09/Dec/11 ]

Author:

{u'login': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-4399 make replica set updating more reliable in c++ driver, remove nodes when no longer present in config
Branch: master
https://github.com/mongodb/mongo/commit/7450bc147428975b6412635ba7d9262e635316e5

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

Generated at Thu Feb 08 03:05:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.