From fe619208f86ccbd5545e24d74f31214c5350e303 Mon Sep 17 00:00:00 2001 From: Konstantin Silin Date: Wed, 29 Mar 2023 19:27:54 +0200 Subject: [PATCH] Add callout on Kafka Streams configurations for production in kafka-streams.adoc --- docs/src/main/asciidoc/kafka-streams.adoc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/src/main/asciidoc/kafka-streams.adoc b/docs/src/main/asciidoc/kafka-streams.adoc index 839d448a705c8..cee41992e1571 100644 --- a/docs/src/main/asciidoc/kafka-streams.adoc +++ b/docs/src/main/asciidoc/kafka-streams.adoc @@ -464,6 +464,11 @@ This is to done to gracefully await the creation of topics that don't yet exist TIP: Alternatively, you can use `kafka.bootstrap.servers` instead of `quarkus.kafka-streams.bootstrap-servers` as you did in the _generator_ project above. +[NOTE] +==== +Once you are ready to promote your application into production, consider changing the above configuration values. While `cache.max.bytes.buffering=10240` will move your records faster through the topology, the default value of `10485760` is more throughput-friendly. Also condider increasing `metadata.max.age.ms` from `500`, which will update cluster metadata quickly, but will generate a lot of redundant requests, to a value closer to the default of `300000`. A `commit.interval.ms` of `1000` is good for exactly-once processing, but might generate excessive load for the default at-least-once processing with the default value of `30000`. +==== + All the properties within the `kafka-streams` namespace are passed through as-is to the Kafka Streams engine. Changing their values requires a rebuild of the application.