diff options
author | Henning Baldersheim <balder@yahoo-inc.com> | 2021-04-13 11:36:14 +0000 |
---|---|---|
committer | Henning Baldersheim <balder@yahoo-inc.com> | 2021-04-13 11:41:24 +0000 |
commit | d086a35f9188318e74f46a95c58f34603a862ec6 (patch) | |
tree | cb2da09cb73d1ec3ed72f0d5b19d6c458a82ee54 /searchcore | |
parent | 5905ac318a39b0258f392924ed0959e55e35e586 (diff) |
Avoid to have a period of a day since that is a normal period in crontab like job control.
Diffstat (limited to 'searchcore')
-rw-r--r-- | searchcore/src/vespa/searchcore/config/proton.def | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/searchcore/src/vespa/searchcore/config/proton.def b/searchcore/src/vespa/searchcore/config/proton.def index cc11384ac18..ec7752368e9 100644 --- a/searchcore/src/vespa/searchcore/config/proton.def +++ b/searchcore/src/vespa/searchcore/config/proton.def @@ -71,8 +71,10 @@ flush.memory.each.maxmemory long default=1073741824 flush.memory.each.diskbloatfactor double default=0.2 ## Age of unflushed content before forcing age prioritization. -## Unit is seconds with 1 day being the default. -flush.memory.maxage.time double default=86400.0 +## Unit is seconds with 31 hours being the default. +## 31 is selected as it is both a prime and (31-24=7) is a prime and hence it will +## not be closer to a multiple of a day for a month, and it will be at least one hour away. +flush.memory.maxage.time double default=111600.0 ## When resource limit for memory is reached we choose a conservative mode for the flush strategy. ## In this case this factor is multiplied with 'maxmemory' and 'each.maxmemory' to calculate conservative values to use instead. |