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

Long-running getlasterror processes build on themselves and hog CPU

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • None

    Description

      If getlasterror has an unfulfillable w, it will basically spinlock until wtimeout runs out. The problem is, this can cause a backlog of getlasterror commands, all spinlocking, which can hog all of the CPU. Perhaps getlasterror should use an exponential backoff to determine sleep time?

      Attachments

        Activity

          People

            Unassigned Unassigned
            kristina Kristina Chodorow (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: