[SERVER-11982] connection error when doing sharded cluster upgrade following recommended procedure Created: 05/Dec/13 Updated: 10/Mar/14 Resolved: 11/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Sharding |
| Affects Version/s: | 2.5.4 |
| Fix Version/s: | 2.6.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Adinoyi Omuya | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | 26qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
The recommended process for doing a sharded cluster version upgrade is:
However, when running this for a 2.4 to 2.5 version upgrade, the following error is thrown when a client (e.g. a mongo process) attempts to run the authSchemaUpgradeStep command on the admin database.
However if the order is changed a bit:
There are no issues upgrading in this order. |
| Comments |
| Comment by Randolph Tan [ 11/Feb/14 ] |
|
Note: if you follow the recommended procedure, you need to call connPoolSync against the mongos before running authSchemaUpgrade |
| Comment by Githook User [ 11/Feb/14 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: Make connPoolSync clear all global connection pools |
| Comment by Githook User [ 11/Feb/14 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: |
| Comment by Randolph Tan [ 04/Feb/14 ] |
|
To workaround this issue, the upgrade procedure should be done as follows: 1. Upgrade config server binaries. |
| Comment by Valeri Karpov [ 12/Dec/13 ] |
|
I can confirm that I've had a similar issue |