Automatic Big SQL transaction log pruning for a high availability-enabled cluster

You can enable automatic Big SQL transaction log pruning for a high availability-enabled cluster. Pruning deletes internal database transaction logs that are no longer needed.

Procedure

To enable automatic pruning, complete the following steps:

  1. Open the Big SQL service in the Ambari dashboard and click Configs > Advanced bigsql-env.
  2. Select Automatic transaction log pruning. This sets the enable_auto_log_prune configuration parameter to enable.
  3. Restart the Big SQL service so that the changed setting can take effect.
    Transaction log files will be pruned daily at midnight.

To prune Big SQL transaction logs manually when HA is enabled, complete the following steps:

  1. Open the Big SQL service in the Ambari dashboard and click Summary > Service Actions.
  2. Select Prune Transaction Logs.