-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Compaction
-
None
-
Storage Engines, Storage Engines - Persistence
-
SE Persistence - 2025-11-21, SE Persistence - 2025-12-05
-
1
There are two flavours of compaction
- A user explicitly running compact on a collection (which also compacts the indexes)
- Background compaction running on tables
The message doesn't distinguish which of these two cases we ran into, which would make it easier to diagnose next time.
[j6:prim] | 2025-09-08T23:17:37.073+00:00 E WT 22435 [conn1739] "WiredTiger error message","attr":{"error":16,"message":{"ts_sec":1757373457,"ts_usec":72797,"thread":"6666:0x7f7be115e700","session_dhandle_name":"file:index-853-4061456052142121388.wt","session_name":"WT_SESSION.compact","category":"WT_VERB_DEFAULT","log_id":1000000,"category_id":12,"verbose_level":"ERROR","verbose_level_id":-3,"msg":"int __wt_block_compact_start(WT_SESSION_IMPL *, WT_BLOCK *):23:Compaction already happening on data handle index-853-4061456052142121388.wt by session 22","error_str":"Device or resource busy","error_code":16}}
If we can add some additional context like "because background compaction was compacting the table", that'd be helpful.