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

Don't block on cache eviction after allocating an oplog slot

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

      Operations can block on cache eviction at any time, and we should ensure that after allocating an oplog slot, we cannot block on cache eviction for longer than some maximum threshold. We otherwise risk delaying replication for extended periods of time.

      We can use the setCacheMaxWaitTimeout for this purpose. I suspect this API has a bit of overhead due to the WT_SESSION::reconfigure() call, so we'll need to investigate that tradeoff.

            Assignee:
            Unassigned Unassigned
            Reporter:
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: