Configuring the Retention Settings for New Kafka Topics
The mf-event-avro-enriched topic, which was added with ArcSight Platform 21.1, occupies storage space on worker nodes where you apply the 'kafka:yes' label. To ensure that the nodes have enough storage space for each topic, you must tune the settings for topic retention. By tuning the storage settings, you allocate storage space for this topic, the existing topics, and other components that use storage on these worker nodes. Please note that this procedure does not interrupt the flow of events through the system.
-
Log in to an ArcSight master node as root.
- To determine the current topic retention storage size for the th-arcsight-avro topic, run the following command:
- To calculate the retention size for each topic, divide the
retention.bytesvalue from Step 2 by two.
The th-arcsight-avro and mf-event-avro-enriched topics will share the same retention size. -
To set the retention size for the th-arcsight-avro topic, in the following command replace {number} with the value calculated in Step 3, and then run it:
- To set the retention size for the mf-event-avro-enriched topic, in the following command replace {number} with the value calculated in Step 3, and then run it:
kubectl exec -n $( kubectl get pods --all-namespaces | grep kafka-0 | cut -d ' ' -f1 ) th-kafka-0 -- /usr/bin/kafka-configs --bootstrap-server th-kafka-svc:9092 --describe --topic th-arcsight-avro | grep retention.bytes
kubectl exec -n $( kubectl get pods --all-namespaces | grep kafka-0 | cut -d ' ' -f1 ) th-kafka-0 -- /usr/bin/kafka-configs --bootstrap-server th-kafka-svc:9092 --alter --topic th-arcsight-avro --add-config retention.bytes={number}
kubectl exec -n $( kubectl get pods --all-namespaces | grep kafka-0 | cut -d ' ' -f1 ) th-kafka-0 -- /usr/bin/kafka-configs --bootstrap-server th-kafka-svc:9092 --alter --topic mf-event-avro-enriched --add-config retention.bytes={number}