Configuring Cassandra compression
This content applies only to On-premises and Client-managed cloud environments
You can customize the compression settings for Cassandra SSTables to best suit your application's requirements. By using compression, you reduce the size of the data written to disk, and increase read and write throughput.
You can configure two types of compression:
- Client-to-server compression
- Compresses the communication between Pega Platform and Cassandra.
- Node-to-node compression (deprecated)
- Compresses the contents of Cassandra SSTables.
prconfig.xml settings.For more information about specifying
settings through the prconfig.xml file, see Changing node settings by modifying the prconfig.xml file.
- Configure client-to-server compression:
If you want to use LZ4 compression, set the value of dnode/cassandra_client_compression to LZ4.
If you want to use Snappy compression, set the value of dnode/cassandra_client_compression to SNAPPY.
If you do not want to use client-to-server compression, set the value of dnode/cassandra_client_compression to NONE.
- Configure node-to-node compression (deprecated):
If you want to compress all node-to-node compression (both inter-data center and intra-data center), set the value of the dnode/yaml/internode_compression property to ALL.
If you want to compress only inter-data center traffic, set the value of the dnode/yaml/internode_compression property to DC.
If you do not want to use node-to-node compression, set the value of the dnode/yaml/internode_compression property to NONE.
Previous topic Best practices for disk space management Next topic Configuring client-to-server compression