Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-12560

Application thread is stuck in forced eviction because of uncommitted updates

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Storage Engines
    • StorEng - Refinement Pipeline

      This ticket is created following the findings in BF-31578. We found that a MongoDB test is stuck because all the application threads are stuck doing forced eviction. However, none of them can make progress because the updates are not committed and visible.

      We have done another change WT-11398 to refresh the application thread's snapshot to allow us to evict the recently committed changes. However, this will not work if all the updates on the page to evict are not committed.

      Instead of being stuck in the force eviction loop, we should tell the application thread to back off in this case.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            chenhao.qu@mongodb.com Chenhao Qu
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: