Investigate solutions to the fsync (lock:true) starvation scenario

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Cluster Scalability
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      With SERVER-78149, users can now issue fsync(lock: true) through mongos which in turn acquires a Global S lock on all the shards. However, the mongos fsync (lock:true) request has a default of a 90s timeout and this may lead to scenarios where the fsyncLock request is never granted, especially when transactions are being heavily used by the users or internally. 

              Assignee:
              Unassigned
              Reporter:
              Nandini Bhartiya
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: