Stuck with long-running transactions that can't be timed out

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.7.0, 4.4.2, 4.2.11, 4.0.22
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v4.4, v4.2, v4.0
    • Execution Team 2020-09-07
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When there are long-running transactions the server can get stuck with the cache full of dirty data because the thread that is responsible for aborting timed-out transactions may become stuck trying to evict data that is pinned in cache by the long-running transactions that it's tasked with aborting.

              Assignee:
              Gregory Noma
              Reporter:
              Bruce Lucas (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              24 Start watching this issue

                Created:
                Updated:
                Resolved: