|
dmitry.agranat Yes, we have similar logging that prints the stats and then prints if 10% of the space is available or not and if compact can proceed or skip.
Below example when it compacts the files and later it gives up because compact cannot recover 10% or 3MB and hence compaction is skipped.
file:test_compact02.wt, WT_SESSION.compact: [WT_VERB_COMPACT] test_compact02.wt: total reviewed 2742 pages, total skipped 0 pages, total wrote 1783 pages
|
file:test_compact02.wt, WT_SESSION.compact: [WT_VERB_COMPACT] test_compact02.wt: 0MB (4096) available space in the first 80% of the file
|
file:test_compact02.wt, WT_SESSION.compact: [WT_VERB_COMPACT] test_compact02.wt: 0MB (4096) available space in the first 90% of the file
|
file:test_compact02.wt, WT_SESSION.compact: [WT_VERB_COMPACT] test_compact02.wt: require 10% or 3MB (3395174) in the first 90% of the file to perform compaction, compaction skipped
|
|
|
dmitry.agranat
As part of PM-2054 we implemented additional logging(WT-8189) and stats(WT-6077) while running compact operation.
Addition loggings include when the compact quits early because the file size is less than 1 MB, compact quits early because of time out, etc.
Can we close this ticket if the details are sufficient?
|