-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
I'm working on SERVER-70201 to interrupt long running WT::compact commands from the MDB layer. This work leverages the WT::compact command interruptibility added in WT-9636.
I'm trying to write a JS test in the MDB layer that interrupts an active WT::compact command. I need WT::compact to check for interrupt sooner – preferably at start. Currently WT::compact checks for interrupt after 100 internal iterations, for which it appears to be very difficult to write a test data workload that runs in any reasonable amount of time – I've only managed to provoke 2 iterations. Furthermore, it would be helpful to surface a single WT log message that compaction did not occur, that can then be checked for – the absence thereof – in the MDB testing to ensure that compaction took place.
Specific requests:
1) Make the interrupt check run the first iteration. Instead of checking interrupt every 100th run, check it the first run and then every 100th.
2) Consistently log a msg when WT::compact decides there's no useful work to do. Currently there's a log msg here if the table data is too small to bother compacting. However, there are two more checks where compact skips but does not log anything.
- is depended on by
-
SERVER-75917 Follow-up ticket to add JS test for MDB layer initiated WT::compact command interrupts
- Closed
-
SERVER-70201 Make compact killable
- Closed
- is duplicated by
-
WT-10910 failed: make-check-nonstandalone on ubuntu2004 [wiredtiger @ 8720a0b3]
- Closed
- related to
-
WT-9636 Provide a way for an application to interrupt a long-running compact command
- Closed