Browse Source

Adds new configuration for panko-expirer

This patch enables limiting count of records panko-expirer is deleting each run.
We need that to avoid expirer failures on huge event databases.

Depends-On: I7ca0ab9e42352645e463c49f8ce58793115543c0
Change-Id: Idc59d4958a3919c6b457fcad083e0d07afe10892
changes/54/753154/4
Martin Magr 9 months ago
parent
commit
7d4f2f500b
1 changed files with 6 additions and 0 deletions
  1. +6
    -0
      deployment/deprecated/panko/panko-api-container-puppet.yaml

+ 6
- 0
deployment/deprecated/panko/panko-api-container-puppet.yaml View File

@ -101,6 +101,11 @@ parameters:
description: >
Cron to delete events from db - Week Day
default: '*'
PankoExpirerBatchSize:
type: number
description: >
Limit number of deleted events in single purge run
default: 500
conditions:
service_debug_unset: {equals : [{get_param: PankoDebug}, '']}
@ -204,6 +209,7 @@ outputs:
panko::expirer::monthday: {get_param: PankoExpirerMonthday}
panko::expirer::month: {get_param: PankoExpirerMonth}
panko::expirer::weekday: {get_param: PankoExpirerWeekday}
panko::expirer::events_delete_batch_size: {get_param: PankoExpirerBatchSize}
service_config_settings:
keystone:
panko::keystone::auth::public_url: {get_param: [EndpointMap, PankoPublic, uri]}


Loading…
Cancel
Save