-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
kafka command raise 'Address Already in used' after configuration #983
Comments
@vhp1360 for Kafka, you should integrate the JMX exporter at the component level. For a broker, you should add it to Other components follow a similar scenario, but may use different environment variable names. |
thanks for reply, could you please provide a link. |
Here is a good reference: https://www.confluent.io/blog/monitor-kafka-clusters-with-prometheus-grafana-and-confluent/ |
thank you, i'm checking in next days and reply. |
hello again. |
"You can inject it by appending the KAFKA_OPTS variable or by adding an EXTRA_ARGS (variable)" Define an environment variable
When you run ...
... the extras args will be added to the overall command. |
thanks. It works. but it isnt suitable. |
The integration depends on how you are starting components. If you are using systemd, you can define |
no I use source. |
What I suggested is the recommended/proper way to pass the extra arguments to Kafka when running
|
many thanks.my problem solved. maybe changing the document which I mentioned at first, helps others |
Hello
I face a issue.
I config my kafka cluster according documentation and I can gather metrics in premetheus, but after changing
kafka-server-class.sh
file according the this project documentation, I couldn't run any kafka commands and I gotAddress Already in used
. this error raise for any ports which I set forjava -javaagent:./jmx_prometheus_javaagent-0.20.0.jar=AnyPort:config.yaml -jar yourJar.jar
The text was updated successfully, but these errors were encountered: