Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-10615

setShardVersion failing "client version differs from config's for collection" message

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker - P1
    • Resolution: Works as Designed
    • Affects Version/s: 2.2.4
    • Fix Version/s: None
    • Component/s: Sharding, Stability
    • Labels:
    • Environment:
      AWS EC2 Linux
    • Operating System:
      Linux

      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.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: