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

Test that LSM is behaving as expected.

    • Type: Icon: Task Task
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None

      We should add some direct tests of LSM logic: e.g., that we don't throttle under "normal" conditions, and that compact reduces simple trees down to one level. For example, if a change means that LSM isn't able to flush chunks under load, that should make a test fail rather than just changing the performance of wtperf.

      Either have Python code look at stats, or walk the metadata and/or the filesystem to check that the final LSM state matches what is expected. Verbose messages could be intercepted to indicate if there is any throttling?

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            michael.cahill@mongodb.com Michael Cahill (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: