-
Notifications
You must be signed in to change notification settings - Fork 199
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
OffsetMonitor stopped producing metrics after disabling anonymous access on SRC and DST Kafka clusters #350
Comments
@yangy0000 - I turned on logging in debug mode and got this complete error log with OffsetMonitor:
Perhaps this will help in some way.
Port 9192 use |
Unfortunately, offset monitor is built on top of SimpleConsumer which doesn't support SASL_SSL protocal. We are planning to fix this too @laosiaudi You can make contributions to this if you are interested. :) |
@yangy0000, @laosiaudi - here's the thing, it's clear - thanks a lot for the info! And at the moment - perhaps there are alternative options, to replace OffsetMonitor with something, for monitoring offset lag - maybe some external utilities? I would be glad to hear any advice, thanks. |
Hi to all!
@yangy0000 - I found strange OffsetMonitor behavior when I disabled ports without encryption and with anonymous access on Kafka clusters SRC and DST. That is, those ports that worked under the
PLAINTEXT
protocol. And only those ports on Kafka clusters, where the protocol isSASL_SSL
, continued to work - that is, with encryption and authorization using theSCRAM
mechanism.And after that, the OffsetMonitor began to produce the following errors in logs:
Is it somehow possible to fix this behavior for me on my own, by correcting some configuration, for example, or do I need to wait for a fix of the uReplicator itself and its new version?
I would be glad to hear any advice, thanks.
The text was updated successfully, but these errors were encountered: