specifies whether incremental and/or full updates will be used
see below
update-interval
(required) interval between Update invocations
–
update-jitter
max. amount of time by which interval may be adjusted for requests dispersal
update_interval / 10
full-update-interval
interval between full updates
–
updates-enabled
if false, cache updates are disabled (except for the first one if !first-update-fail-ok)
true
first-update-fail-ok
whether first update failure is non-fatal
false
task-processor
the name of the TaskProcessor for running DoWork
main-task-processor
config-settings
enables dynamic reconfiguration with CacheConfigSet
true
exception-interval
Used instead of update-interval in case of exception
update_interval
additional-cleanup-interval
how often to run background RCU garbage collector
10 seconds
is-strong-period
whether to include Update execution time in update-interval
false
testsuite-force-periodic-update
override testsuite-periodic-update-enabled in TestsuiteSupport component config
–
failed-updates-before-expiration
the number of consecutive failed updates for data expiration
–
has-pre-assign-check
enables the check before changing the value in the cache, by default it is the check that the new value is not empty
false
Update types
full-and-incremental: both update-interval and full-update-interval must be specified. Updates with UpdateType::kIncremental will be triggered each update-interval (adjusted by jitter) unless full-update-interval has passed and UpdateType::kFull is triggered.
only-full: only update-interval must be specified. UpdateType::kFull will be triggered each update-interval (adjusted by jitter).
only-incremental: only update-interval must be specified. UpdateType::kFull is triggered on the first update, afterwards UpdateType::kIncremental will be triggered each update-interval (adjusted by jitter).
testsuite-force-periodic-update
use it to enable periodic cache update for a component in testsuite environment where testsuite-periodic-update-enabled from TestsuiteSupport config is false
By default, update types are guessed based on update intervals presence. If both update-interval and full-update-interval are present, full-and-incremental types is assumed. Otherwise only-full is used.
See also
dump::Dumper for more info on persistent cache dumps and corresponding config options.