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

Reduce tsan history_size to 4 to address OOM errors

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 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

      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@mongodb.com Lynne Wang
            Reporter:
            lynne.wang@mongodb.com Lynne Wang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: