Repository navigation
Property table.compaction.minor.age default value, should it be zero? #6532
Description
The property, new in 4.0.0, has a default value of 10 minutes which will change the behavior of minor compactions on upgrade from an earlier release. I'm wondering if the default value should disable this functionality to preserve prior behavior.
Activity
ddanielr commentedon Oct 7, 2026
The comment for the property states:
The default value of this property is set to such a high value that is should never cause a minor compaction..The property was added in #4853 which switches the behavior from a
idletrigger to a max age.Looking at LargestFirstMemoryManager, setting the behavior to zero doesn't seem like it would match earlier code behavior either.
dlmarion commentedon Oct 7, 2026
Ok, then maybe we set the default value a larger amount? 10 minutes doesn't seem like it's "such a high value that is should never cause a minor compaction".
dlmarion commentedon Oct 20, 2026
@keith-turner and I discussed. He said that this property was added to support the eventual consistency time for ScanServers, which do a metadata refresh. @keith-turner said that there is no issue setting this to a much larger value to provide a behavior consistent with prior releases. Maybe Integer.MAX_VALUE or something equivalent to some number of months.
Amemeda commentedon Oct 26, 2026
I dont think Integer.MAX_VALUE is valid default value format for TIME_DURATION. It can be months in the form of days, how many months would be good? I am testing the default value with 4 months