[SERVER-14248] ERROR: error upgrading config database to v5::caused by:: newer version 5 of mongo config metadata is required, current version is 4, need to run mongos with --upgrade Created: 13/Jun/14  Updated: 10/Dec/14  Resolved: 13/Jun/14

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

Type: Question Priority: Major - P3
Reporter: Pratik Gadiya [X] Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

I have deployed a sharded cluster following the steps given in the mongodb documentation.
Currently, I have deployed one shard (i.e. single replica set ) in the cluster for dev purpose.

My configuration for the sharded cluster is as follows :

1) Server 1 ( IP = x.x.x.1 ): -
1 mongos, 1 config server, 1 repl node ( lets say Primary )
2) Server 2 ( IP = x.x.x.2 ): -
1 mongos, 1 config server, 1 repl node ( lets say Secondary )
3) Server 3 ( IP = x.x.x.3 ): -
1 mongos, 1 config server, 1 repl node ( lets say Arbiter )

All the three servers are of mongo version 2.4.9 and deployment is over three different servers

Accidentally on Server 3 machine got rebooted and I updated the yum repository due to which mongo version got updated to 2.6.1.

Now, when I try to restart the services, all the other services gets restarted properly except mongos service on server 3( as this is the only node which got updated, other nodes are on 2.4.9 )

Mongos service result in to an error as follows :

ERROR: error upgrading config database to v5::caused by:: newer version 5 of mongo config metadata is required, current version is 4, need to run mongos with --upgrade

Please let me know how can I overcome this problem

( Note : All of my shard elements are working on different ports i.e. mongos is on 27022, config servers is on 27021 and the replica set elements is on 27020 )

Thanks,
Pratik



 Comments   
Comment by Thomas Rueckstiess [ 13/Jun/14 ]

Hi Pratik,

MongoDB 2.6 uses a different metadata format and would require you to upgrade the metadata of your cluster, according to these instructions.

If you're not planning to upgrade the entire cluster to 2.6, then you need to downgrade the accidentally upgraded server (server 3) back to 2.4.9. Instructions for downgrades can be found on our documentation page Downgrade MongoDB from 2.6. You may have to do this manually.

Also please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-users group (http://groups.google.com/group/mongodb-user) or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group.

Regards,
Thomas

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