Summary
We don't have any performance test for disk space usage in place and currently we are relying on mongodb and customers to report any disk usage regressions, which is not good. We should be able to catch that earlier in our own testing

Motivation

• Does this affect any team outside of WT?
  No

• How likely is it that this use case or problem will occur?
  N/A

• If the problem does occur, what are the consequences and how severe are they?
  (A minor annoyance at a log message? Performance concern? Outage/unavailability? Test Failure?)

• Is this issue urgent?
  (Does this ticket have a required timeline? What is it?)
  No

Acceptance Criteria (Definition of Done)
(When will this ticket be considered done? What is the acceptance criteria for this ticket to be closed?)

• Testing
  (What all testing needs to be done as part of this ticket? Unit? Functional? Performance?Testing at MongoDB side?)

• Documentation update
  (Does this ticket require a change in the architecture guide? If yes, please create a corresponding doc ticket.)

[Optional] Suggested Solution
(Is there any suggested solution to handle this issue? Is it related to any existing WT ticket? Is it related to any previous issue fixed? If yes, link the WT ticket number using related to, depends on, dependent on by links)