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

Call to setFeatureCompatibilityVersion sometimes hangs when upgrading from 4.2 to 4.4 on sharded cluster

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Incomplete
    • None
    • None
    • Upgrade/Downgrade
    • None
    • ALL
    • Hide

      1. Create a mongo 4.2 sharded cluster
      2. Upgrade the binaries to 4.4
      3. Call setFeatureCompatibilityVersion on mongos

      Show
      1. Create a mongo 4.2 sharded cluster 2. Upgrade the binaries to 4.4 3. Call setFeatureCompatibilityVersion on mongos

    Description

      I've noticed that after upgrading a 4.2 sharded cluster to 4.4, the call to setFeatureCompatibilityVersion sometimes hangs. I've set a 10 minute timeout on the command and it is reached quite often.

      I can't reproduce this problem all the time. It will usually take about 10s for the command to run normally. I've had cases where it reaches the 10 minutes timeout and other cases where it takes much longer than 10s but still completes within the 10 minute timeout. The logs for mongos don't seem to indicate any problem.

      I'm using the latest versions of 4.2 and 4.4.

      Attachments

        Activity

          People

            dmitry.agranat@mongodb.com Dmitry Agranat
            simon.bernier-st-pierre@ubisoft.com Simon Bernier St-Pierre
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: