Skip to content

Conversation

@darinspivey
Copy link
Contributor

When using multi topics (or regex), when disconnected topic partitions are found, it will recreate their consumers. The logging statement for this was quite noisy in a production environment. Change the code to only log if it finds missing partitions, and also log the topic names so that this functionality can be traced in logs.

Fixes: #389

When using `multi` topics (or regex), when disconnected topic partitions
are found, it will recreate their consumers. The logging statement for
this was quite noisy in a production environment. Change the code to
only log if it finds missing partitions, and also log the topic names so
that this functionality can be traced in logs.

Fixes: streamnative#389
@darinspivey
Copy link
Contributor Author

@BewareMyPower do you mind having a look at this small change? The info! logs are blowing up our logging in production :)

cc: @chamons

Copy link
Contributor

@chamons chamons left a comment

Choose a reason for hiding this comment

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

When I originally info! this I didn't realize how often this would hit. Good catch.

@BewareMyPower BewareMyPower merged commit 5dfd10c into streamnative:master Feb 1, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Logging is too noisy for multi update_topics

3 participants