Writers can get stuck in cache eviction without rolling back transactions in order to make progress

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Storage Engines, Storage Engines - Server Integration
    • ALL
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      For a workload with many threads performing medium-sized writes (unlike SERVER-61909 where there is a single large transaction which cannot fit in cache), especially one with prepared transactions since those cannot be rolled back, we can end up in a scenario where eviction cannot make meaningful progress. The threads performing the writes are being co-opted into performing eviction and cannot return until sufficient eviction progress is made, so they can essentially all become stuck as a result.

              Assignee:
              Unassigned
              Reporter:
              Gregory Noma
              Votes:
              1 Vote for this issue
              Watchers:
              57 Start watching this issue

                Created:
                Updated:
                Resolved: