Reduce tsan history_size to 4 to address OOM errors

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0, 8.0.0-rc12
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • Fully Compatible
    • ALL
    • v8.0
    • QO 2024-07-08
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      TSAN's history_size had previously been increased to alleviate an issue with WiredTiger's complex concurrency model requiring more stacks to capture suppressions. However, this is causing several instances of an OOM error because TSAN is consuming too much memory. Since the original WiredTiger issue has been fixed in this ticket, we can set the history_size back to 4 to resolve the OOM error and decrease resource usage.

              Assignee:
              Lynne Wang
              Reporter:
              Lynne Wang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: