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

Primary mongod instance stops serving traffic every few (5) hours

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Incomplete
    • Icon: Major - P3 Major - P3
    • None
    • 3.0.12
    • Performance, WiredTiger
    • None
    • ALL

    Description

      A running primary node' throughput degrades over time. Switching primary<->secondary solved the problem. As a precaution, we proactively shutdown the old primary once its secondary so that its ready for the next switch. MMS graph showing the degradation attached. This happens to primary nodes running WiredTiger. MMAP is not affected. We ran into this when we re-synced one of the secondaries nodes with storage engine set to WT and promoted it as primary

      Attachments

        1. diagnostic.data.3.2.10.io1.tar.gz
          14.62 MB
        2. diagnostic.data.3.2.9.io1.tar.gz
          12.50 MB
        3. MongoDB-3.2.10-diagnostic.png
          MongoDB-3.2.10-diagnostic.png
          132 kB
        4. MongoDB-3.2.9-diagnostic.png
          MongoDB-3.2.9-diagnostic.png
          135 kB
        5. s26021_3210.png
          s26021_3210.png
          70 kB
        6. s26021_329.png
          s26021_329.png
          76 kB
        7. Screen Shot 2016-09-08 at 2.13.08 PM.png
          Screen Shot 2016-09-08 at 2.13.08 PM.png
          745 kB
        8. Screen Shot 2016-09-09 at 12.00.12 AM.png
          Screen Shot 2016-09-09 at 12.00.12 AM.png
          388 kB

        Activity

          People

            kelsey.schubert@mongodb.com Kelsey Schubert
            francis@wizrocket.com Francis Pereira
            Votes:
            1 Vote for this issue
            Watchers:
            12 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: