[SERVER-18651] Cluster upgrade from 2.6.9 to 3.0.3 error: no such cmd: _getUserCacheGeneration Created: 26/May/15 Updated: 18/Aug/15 Resolved: 26/May/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Sharding |
| Affects Version/s: | 3.0.3 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Marcin Lipiec | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Participants: | |||||
| Description |
|
We have followed upgrade procedure for sharded cluster from 2.6 to 3.0. After successful upgrading of cluster's meta data, we have upgraded one of our mongos processes and started frequently (few per minute) seeing the following errors: 2015-05-26T10:50:44.622+0200 I NETWORK [UserCacheInvalidator] scoped connection to mongo1:27019,mongo2:27019,mongo3:27019 not being returned to the pool } Are those erros something we should worry about? Can we proceed with the upgrade? |
| Comments |
| Comment by Kaloian Manassiev [ 26/May/15 ] |
|
This is correct. The error message is just transient until the config servers are upgraded. Please refer to the MongoDB upgrade guide for the steps. |
| Comment by Marcin Lipiec [ 26/May/15 ] |
|
Actually we've just upgraded only our mongos processes. As it seems we should continue upgrading our config servers, slaves and primaries from 2.6.9 to 3.0.3. |
| Comment by Kaloian Manassiev [ 26/May/15 ] |
|
Hi Marcin, This error means that on of your config servers does not support the _getUserCacheGeneration command. This command was added in 2.6.10 and you say you are upgrading from 2.6.9. My suspicion is that one of your config servers is not actually upgraded and is still at 2.6.9. Would you mind attaching the error logs from each individual config server (at least the startup lines so I can see the version). Thanks, |