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

Explore if we can use curOp to log all active operations if we fail to acquire the RSTL during step up/step down

XMLWordPrintableJSON

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

      Due to SERVER-90775 we aren't able to print all stack traces anymore before fasserting when we fail to acquire the RSTL on step up or step down. This information was critical to diagnosing what could be deadlocked or stalled during this time and without it we often end with incomplete investigations.

      We do have access to the lock manager dump, but without more information about what each thread is doing, it is often hard to figure out what is going on. We might be able to log curOp output to give us additional information.

            Assignee:
            Unassigned Unassigned
            Reporter:
            samy.lanka@mongodb.com Samyukta Lanka
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: