Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Configuring purge cycle settings

Updated on April 5, 2022

You can use dynamic system settings to configure different aspects of a post-archive purge cycle, for example, the duration of a purge cycle. Use these settings to improve performance during purge cycles and control the intervals at which purge cycles occur.

  1. In the navigation panel, click App.
  2. On the Classes tab, in the text box, enter Data-Admin-System-Settings.
  3. Click the Data-Admin-System-Settings class.
  4. In the Dynamic System Settings table, select the system setting that you want to configure from the following options.
    dataarchival/purgeForceLoggingEnabled
    Sets logging on or off 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. The default value is True, which indicates that logging to the system console is enabled.
    dataarchival/purgeQueryTimeoutInMinutes
    Sets a Java Database Connectivity (JDBC) time-out on the URL connection to PostgreSQL during a purge query. The default value is 15.
    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.
    dataarchival/purgeQueryPacingInSeconds
    Sets pacing to pause purge in between queries during a purge action to allow other operations to access the database. The default value is 0.
    dataarchival/purgeMaxDurationInMinutes
    Sets the max duration for an entire purge cycle such that no new classes will be purged when the limit is reached. However, the class being purged will complete normally. The default value is 0.
    dataarchival/purgeBulkDeleteBatchSize
    Sets the batch size for the bulk delete operation of records in the Elasticsearch index. The default value is 1000.
    dataarchival/purgeQueryLimit
    Sets the number of records that a subquery delivers to the delete statement. The default value is 100000.
  5. In the Value field, enter a value for the system setting that you select.
  6. Click Save.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us