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

setShardVersion configdb string mismatch during config rs upgrade

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • ALL
    • Sharding E (01/08/16)

    Description

      The shard will return an error on setShardVersion if it still has the old non-repl config server string.

      Example error:

      Assertion: 10429:setShardVersion failed shard: csrsUpgrade-rs0:csrsUpgrade-rs0/ren-desktop:20000,ren-desktop:20001,ren-desktop:20002 { configdb: { stored: "ren-desktop:20006,\
      		 
          ren-desktop:20007,ren-desktop:20008", given: "csrs_upgrade-csrs/ren-desktop:20006,ren-desktop:20011,ren-desktop:20012" }, ok: 0.0, errmsg: "mongos specified a different config database string : stored : ren-desktop:20006,ren-deskto\
      		 
          p:20007,ren-desktop:20008 vs given : csrs_upgrade-csrs/ren-...", code: 125 }

      Attachments

        1. csrs_upgrade.js
          9 kB
        2. csrs_upgrade.js
          5 kB

        Issue Links

          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-21995 Queries against sharded collections fail after upgrade to CSRS due to caching of config server string in setShardVersion

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              spencer@mongodb.com Spencer Brody (Inactive)
              randolph@mongodb.com Randolph Tan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: