Transaction log cleanup

HCP maintains a transaction log of all create, delete, purge, prune, and disposition operations performed on objects. HCP uses this log to respond to operation-based queries issued through the metadata query API.

HCP adds and deletes records in the transaction log as follows:

When a user or application creates an object, HCP adds a creation record to the log.

When a user or application deletes an object from a namespace that does not have versioning enabled, HCP deletes the applicable creation record from the log and adds a deletion record.

When a user or application deletes an object from a namespace that has versioning enabled, HCP adds a deletion record to the log but does not delete the creation record.

When a user or application purges an object, HCP deletes all the creation and deletion records for all versions of the object from the log and adds a purge record for the most recent version.

When HCP prunes a version of an object, it deletes the applicable creation record from the log and adds a prune record.

When the disposition service deletes an object, HCP deletes the applicable creation record from the log and adds a disposition record.

Deletion, purge, prune, and disposition records contain only object metadata. You can configure the garbage collection service to delete these records after a specified amount of time. If you do this, each time the service runs, it checks the log for records that are eligible to be deleted and, if it finds any, deletes them.

If you don’t configure the garbage collection service to delete deletion, purge, prune, and disposition records from the transaction log, they remain in the log indefinitely.

For any given namespace, the applicable tenant administrator can choose whether HCP should keep records of delete, purge, prune, and disposition operations if the namespace has ever had versioning enabled. If the tenant administrator chooses not to keep these records, they are immediately eligible to be deleted from the log regardless of the garbage collection service configuration.

While the transaction log contains any deletion, purge, prune, or disposition records for a namespace, the namespace cannot be deleted. If a tenant administrator cannot delete an apparently empty namespace, a possible reason is that the transaction log contains one or more of these records. In this case, have the tenant administrator disable the option to keep these records for that namespace.

Note: A namespace with versioning enabled can be deselected from replication while the owning tenant is included in an active/active replication link. In this situation, deletion, purge, prune, and disposition records for objects in the namespace are not deleted from the transaction log, regardless of the garbage collection service configuration, unless the namespace option to keep those records is disabled.

Trademarks and Legal Disclaimer

© 2017 Hitachi Data Systems Corporation. All rights reserved.