Long-running getlasterror processes build on themselves and hog CPU

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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?

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

              Created:
              Updated:
              Resolved: