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

Configure tests to avoid rollback due to cache pressure

    • Type: Icon: Build Failure Build Failure
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT10.0.0, 4.4.0-rc11, 4.7.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • 2
    • Storage - Ra 2020-06-29

      unit-test-long failed on ! Ubuntu 18.04

      Host: ec2-3-90-83-115.compute-1.amazonaws.com
      Project: WiredTiger (develop)
      Commit: diff: WT-6175 Bound the amount of updates in cache (2nd attempt) (#5809)

      Adds a new "updates" target/trigger pair (to the existing "clean" and "dirty" limits) tracking the total amount of "small" objects in cache (generally inserts and updates). These default to a fraction of the dirty limits.

      • Switch to counting updates directly. On the plus side, this moves a field from WT_PAGE to WT_PAGE_MODIFY. On the negative, we're doing extra atomic increments on every allocation. | 17 Jun 20 02:12 UTC
        Evergreen Subscription: ; Evergreen Event:

      Task Logs

            Assignee:
            michael.cahill@mongodb.com Michael Cahill (Inactive)
            Reporter:
            xgen-evg-user Xgen-Evergreen-User
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: