[SERVER-8523] Secondaries running 2.0 not detected by 2.4 mongos during 2.2 -> 2.4 upgrade process Created: 12/Feb/13  Updated: 11/Jul/16  Resolved: 14/Feb/13

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 2.4.0-rc1

Type: Bug Priority: Major - P3
Reporter: Michael O'Brien Assignee: Greg Studer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File bug1.js    
Issue Links:
Related
Operating System: ALL
Participants:

 Description   

No mongod 2.0 processes should be running when the 2.2->2.4 upgrade process takes place and the 2.4 mongos attempts to detect any running processes and order to abort safely.
However with secondaries (i haven't yet tried it to see what happens if they are primaries) running 2.0 the mongos seems to miss them and continue the upgrade anyway.



 Comments   
Comment by auto [ 14/Feb/13 ]

Author:

{u'date': u'2013-02-12T16:02:57Z', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-8523 correctly parse shard host strings from config server for config upgrade
Branch: master
https://github.com/mongodb/mongo/commit/e02bc698e6926e3bd074f2dab5f902d60a3e44a9

Comment by Greg Studer [ 12/Feb/13 ]

Issue is incorrect use of ConnectionString when parsing host strings.

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