[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: |
|
||||
| Issue Links: |
|
||||
| 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. |
| 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: |
| Comment by Greg Studer [ 12/Feb/13 ] |
|
Issue is incorrect use of ConnectionString when parsing host strings. |