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

Unable to upgrade config metadata from v3 to v4 - 13127 getMore: cursor didn't exist on server, possible restart or timeout?

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 2.4.0, 2.4.1
    • Fix Version/s: 2.4.2, 2.5.0
    • Component/s: Sharding
    • Labels:
      None
    • Environment:
    • Operating System:
      ALL
    • Steps To Reproduce:
      Hide

      1.) Install mongos 2.4.1 on a machine
      2.) Run mongos --configdb dbconf1:27019,dbconf2:27019,dbconf3:27019 --upgrade
      3.) 20 minutes later, receive timeout.

      Show
      1.) Install mongos 2.4.1 on a machine 2.) Run mongos --configdb dbconf1:27019,dbconf2:27019,dbconf3:27019 --upgrade 3.) 20 minutes later, receive timeout.

      Description

      When trying to perform an upgrade on the config servers, we get a timeout issue.

      [code]
      ERROR: error upgrading config database to v4 :: caused by :: error upgrading config database from v3 to v4 :: caused by :: could not copy config.chunks to config.chunks-upgrade-514cfc77fc5d397af47be301 :: caused by :: could not copy data into new collection :: caused by :: 13127 getMore: cursor didn't exist on server, possible restart or timeout?
      [/code]

      Our database consists of 18312, and of those, 16790 belong to a single collection.

      I have attempted to repeat the upgrade many times, and the issue continues to occur.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: