Exclude waitForWriteConcernMillis from workingMillis

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Replication
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      We should consider waitForWriteConcern as CurOp timer blocked state and exclude it from workingMillis. 

      Currently, there is at least one instance where wait for write concern overlaps with waiting for locks. We can try moving when the wait for write concern timer starts as conceptually, it should not require locks to achieve write concern.

            Assignee:
            Unassigned
            Reporter:
            Shin Yee Tan
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: