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

error 13388 shard version not ok in Client::Context

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: 2.2.3
    • Fix Version/s: None
    • Component/s: Querying
    • Labels:
      None
    • Environment:
      Linux 64 Bit
    • Operating System:
      Linux
    • Steps To Reproduce:
      Hide

      mongos> db.adminCommand( "flushRouterConfig" )
      { "flushed" : true, "ok" : 1 }
      mongos> db.offer.count({"smallPicture.0":{$exists:true}})
      Wed Mar  6 18:03:31 uncaught exception: count failed: {
          "shards" : {
               
          },
          "cause" : {
              "errmsg" : "13388 [offerStore.offer] shard version not ok in Client::Context: version mismatch detected for offerStore.offer, stored major version 5788 does not match received 5787 ( ns : offerStore.offer, received : 5787|0||000000000000000000000000, wanted : 5788|0||000000000000000000000000, send )",
              "ok" : 0
          },
          "ok" : 0,
          "errmsg" : "failed on : offerStoreDE2"
      }

      Show
      mongos> db.adminCommand( "flushRouterConfig" ) { "flushed" : true, "ok" : 1 } mongos> db.offer.count({"smallPicture.0":{$exists:true}}) Wed Mar 6 18:03:31 uncaught exception: count failed: { "shards" : { }, "cause" : { "errmsg" : "13388 [offerStore.offer] shard version not ok in Client::Context: version mismatch detected for offerStore.offer, stored major version 5788 does not match received 5787 ( ns : offerStore.offer, received : 5787|0||000000000000000000000000, wanted : 5788|0||000000000000000000000000, send )", "ok" : 0 }, "ok" : 0, "errmsg" : "failed on : offerStoreDE2" }

      Description

      When we run a slow query, we encounter the "13388 shard version not ok in Client::Context" error even when we flush the router config just before sending the query.

      Does this mean that Mongo can't execute a long running query because the config changed in the meanwhile? How to cope with?

        Attachments

        1. failed_dd_master.log
          9.53 MB
        2. ok_master.log
          9.44 MB
        3. ver_not_ok.js
          0.8 kB

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: