Housekeeping Component Remover
The Housekeeping Component Remover is responsible for automatically deleting components that have exceeded their configured time to live (TTL).
Scenario
When a component in the database is older than the time-to-live value defined in the configuration, it is considered stale and will be deleted from the database.
Configuration
Property Grouping: ipf.debulker.housekeeping.stale-component-remover
| Key | Description | Default Value |
|---|---|---|
ipf.debulker.housekeeping.stale-component-remover.scheduler-restart-settings.min-backoff |
Minimum delay before restarting the scheduler after a failure. |
|
ipf.debulker.housekeeping.stale-component-remover.enabled |
Enables or disables the stale component remover. |
|
ipf.debulker.housekeeping.stale-component-remover.scheduler-restart-settings.max-backoff |
Maximum delay before restarting the scheduler after a failure. |
|
ipf.debulker.housekeeping.stale-component-remover.initial-delay |
Initial delay before the first housekeeping task is triggered. |
|
ipf.debulker.housekeeping.stale-component-remover.scheduler-restart-settings.jitter-factor |
Jitter factor applied to the scheduler’s backoff strategy to randomize restarts. |
|
ipf.debulker.housekeeping.stale-component-remover.component-max-age |
Maximum allowed age for a component before it is considered stale. |
|
ipf.debulker.housekeeping.stale-component-remover.housekeeping-interval |
Interval between consecutive housekeeping executions. |
|