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

Mongo flush critical alert

    XMLWordPrintableJSON

Details

    • Icon: Question Question
    • Resolution: Done
    • Icon: Minor - P4 Minor - P4
    • None
    • None
    • None
    • Red Hat Enterprise Linux Server release 5.7 (Tikanga). Three node replica set.
    • Minor Change

    Description

      We have three node production replica set. We received critical flush alert when we were adding images to product catalog, what increased from ~150k MB to ~330KMB the product catalog collection.
      The primary flush took 5ms at about that time where the secondary and tertiary took +500ms.
      Currently, we have Mongo flush critical alert set to 400ms.

      We would like to know why it takes much more time between Primary/master and slaves.
      Should we increase current threshold for that alert?

      Any information and help is appreciated.
      Thank you,
      Aggie Filarska

      Attachments

        Activity

          People

            scotthernandez Scott Hernandez (Inactive)
            afilarska Aggie Filarska
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: