[SERVER-10615] setShardVersion failing "client version differs from config's for collection" message Created: 23/Aug/13  Updated: 10/Dec/14  Resolved: 27/Aug/13

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

Type: Bug Priority: Blocker - P1
Reporter: Rolando Berrios Assignee: Unassigned
Resolution: Done Votes: 0
Labels: sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

AWS EC2 Linux


Operating System: Linux
Participants:

 Description   

Following an earlier issue with Mongo Config servers being out of sync and manually resyncing the Config DBs, I'm seeing the following error message in my logs and having trouble writing to the database:

Aug 23 18:47:14 ip-10-145-194-175 S=[Mongos] Env=[prod] DBCluster=[aggregatetraffic]: Fri Aug 23 18:47:14 [conn51] going to retry checkShardVersion host: jawsv2:27017

{ oldVersion: Timestamp 0|0, oldVersionEpoch: ObjectId('000000000000000000000000'), ns: "DB.TrafficSourcesByHour", version: Timestamp 658000|0, versionEpoch: ObjectId('51b219de2543df504bd2058d'), globalVersion: Timestamp 644000|0, globalVersionEpoch: ObjectId('51b219de2543df504bd2058d'), errmsg: "client version differs from config's for collection 'DB.TrafficSourcesByHour'", ok: 0.0 }

I've tried restarting all mongos instances, stepping down the primary, flushing the router configs, all without any success.



 Comments   
Comment by Rolando Berrios [ 26/Aug/13 ]

Turns out I missed a mongos instance when cycling through them all. Once I restarted the last few everything was fine.

Thanks for the response.

Comment by Eliot Horowitz (Inactive) [ 26/Aug/13 ]

Assuming you are more interested in getting up that diagnosing, can you try restarted all mongod processes, then mongos?

If that doesn't work, can you send a mongodump of the config servers?

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