Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tweak Kafka Streams config #1043

Merged
merged 1 commit into from
Jan 30, 2024
Merged

Tweak Kafka Streams config #1043

merged 1 commit into from
Jan 30, 2024

Conversation

nscuro
Copy link
Member

@nscuro nscuro commented Jan 28, 2024

Some config values are a bit too excessive for production use, in particular for:

  • commit.interval.ms
  • cache.max.bytes.buffering
  • metadata.max.age.ms

Quoting the Quarkus docs (https://quarkus.io/guides/kafka-streams):

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 consider 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.

@nscuro nscuro added the enhancement New feature or request label Jan 28, 2024
Some config values are a bit too excessive for production use, in particular for:

* `commit.interval.ms`
* `cache.max.bytes.buffering`
* `metadata.max.age.ms`

Quoting the Quarkus docs (https://quarkus.io/guides/kafka-streams):

"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 consider 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`."

Signed-off-by: nscuro <nscuro@protonmail.com>
Copy link
Collaborator

@VinodAnandan VinodAnandan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link

sonarcloud bot commented Jan 28, 2024

Quality Gate Passed Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@nscuro nscuro merged commit ff91529 into main Jan 30, 2024
11 checks passed
@nscuro nscuro deleted the kstreams-config branch January 30, 2024 12:30
@nscuro nscuro added this to the 0.3.0 milestone Feb 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants