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

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

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

      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 Unassigned
            Reporter:
            nandini.bhartiya@mongodb.com Nandini Bhartiya
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: