You are currently reviewing an older revision of this page.

DRAFT KB-XXXX How the Transaction Log is Maintained in New Appian Architecture FAQ

Q: Where is the transaction log located?

A: Kafka and Zookeeper each have a directory where they write their data files (by default Kafka's data is in <appian home>/services/data/kafka-logs and zookeeper's data is in <appian home>/services/data/zookeeper). Those files make up the actual transaction logs for all K engines so they should not be touched.

Q: How many files are there and do I have to manually go in and clean it up?

A: The number of files will vary and is not really important to worry about because Kafka and Zookeeper will automatically clean up (delete) older files which they no longer need. Appian automatically delete transactions out of kafka once they are older than the 3rd most recent checkpoint for the relevant engine.

Q: Is the cleanup process configurable?

A: How they clean up is somewhat configurable based on how frequently the engines checkpoint. The more frequently they checkpoint, the less data will be kept in the transaction logs. Checkpoint frequency configuration docs are here: Configuring Application Checkpointing

Q: Would checkpointing more frequently influence the maintenance process of the transaction log?

A: By default, old checkpoints do not get deleted. They are just moved to an archive location (<Appian Home>/services/data/archived by default) so checkpointing more frequently will use up more disk space for the checkpoint images. The cleanupArchives script should be used to clean up these old checkpoint images (which is mentioned in the checkpoint documentation).

 

Affected Versions

  • This article applies to Appian 17.3 and later.