Configuring purge cycle settings
Use dynamic system settings to configure aspects of a post-archive purge cycle, such as the duration of a purge cycle, to improve performance during purge cycles, and to control the intervals at which purge cycles occur.
- In the navigation pane of Dev Studio, click.
- In the Setting Purpose column, click the
filter icon and filter the column by entering
dataarchival.
- To set the number of records that a subquery
delivers to the delete statement, select
dataarchival/purgeQueryLimit.
The default value is 0 (all entries ready to be purged are purged).
- To control the size of each batch of cases during
the purge process,
selectdataarchival/purgeBatchSize.
This option uses purgeQueryLimit and divides it by this the value used for this setting to determine how many purging loops Pega Platform.
For example, the purgeQueryLimit is 100, and the purgeBatchSize is 50, and your archival policy is set on two case hierarchies with 10 sub-cases. The process purges all 10 subclasses when purging all 100 records for each individual pyObjClass. Because the batch size is 50, the job runs two purge loops to purge 100 records, purging 50 records each loop.
The default value is 1000.
- To control what is logged in the system console
for all purge and archive components, including the crawler, the archiver,
the indexer, and the purger, enable or disable logging by selecting
dataarchival/purgeForceLoggingEnabled.
The default value is True, which indicates that logging to the system console is enabled.
- To set a Java Database Connectivity (JDBC)
time-out on the URL connection to PostgreSQL during a purge query, select
dataarchival/purgeQueryTimeoutInMinutes.
Note: This setting does not apply to data source connections that are defined for Apache Tomcat servers and other external app servers, because these servers specify the time-out directly in the data source configuration. The default value is 15 (minutes).
- To set the pacing to pause the purge in between
queries during a purge action, to allow other operations to access the
database, select
dataarchival/purgeQueryPacingInSeconds
The default value is 0.
- To set the batch size for the bulk delete
operation of records in the Elasticsearch index, select
dataarchival/purgeBulkDeleteBatchSize.
The default value is 1000.
- To set the number of records that a subquery
delivers to the delete statement, select
dataarchival/purgeQueryLimit.
- In the Value field, enter a value for the system setting that you select.
- Click Save.
Previous topic Configuring archive cycle settings Next topic Configuring expunge cycle settings