The long-running part of the compact command is when we actually call into WT::compact. This means there currently a compact command essentially can't be killed once it has started. WT-9636 added the ability to interrupt WT::compact, so we should make use of it here.
- causes
-
SERVER-75917 Follow-up ticket to add JS test for MDB layer initiated WT::compact command interrupts
- Closed
- depends on
-
WT-10897 Make WT::compact command more test friendly in the MDB layer
- Closed
-
WT-9636 Provide a way for an application to interrupt a long-running compact command
- Closed
- is related to
-
SERVER-75814 MDB compact commands running in testing aren't actually exercising WT compact because the data size is too small and WT skips it
- Open
- related to
-
SERVER-79869 The WiredTiger event handler is not used correctly when calling compact
- Closed