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

very high IO utilization after upgrade from mongo 3.6 to 4.0.18

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • 4.0.18
    • None
    • None
    • None
    • ALL

    Description

      We upgraded our sharded cluster from mongo 3.6 to 4.0.18 on Linux Stretch. Since then IO utilization is almost always at 100%Unable to render embedded object: File ( Almost all monitored metrics look worse than before the upgrade) not found. I'll attach a screenshot where you can see that IO utilization went up to almost constant 100% at around 0:00 o'clock when we upgraded the shard to mongodb 4.0.18 

      We did not yet set FCV to 4.0 to allow our deployment to run without enabling these features for a burn-in period to ensure the likelihood of downgrade is minimal - as suggested in mongodb's documentation.

      Any help is greatly appreciated because this issue becomes critical!

      Attachments

        1. Bildschirmfoto 2020-06-10 um 11.10.04.png
          Bildschirmfoto 2020-06-10 um 11.10.04.png
          282 kB
        2. disk_reads.png
          disk_reads.png
          152 kB
        3. PrimaryAfterDowngrade.png
          PrimaryAfterDowngrade.png
          713 kB
        4. PrimaryAfterUpgrade.png
          PrimaryAfterUpgrade.png
          1.02 MB

        Issue Links

          Activity

            People

              dmitry.agranat@mongodb.com Dmitry Agranat
              kay.agahd@idealo.de Kay Agahd
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: