-
Notifications
You must be signed in to change notification settings - Fork 21
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
Kafkamanager does not see JMX port #70
Comments
JMX_PORT is included in the "service.conf". Kafka container entrypoint.sh will source the service.conf file. Kafka should already start with JMX_PORT. KafkaManager collects the metrics via the JMX_PORT. If JMX_PORT is not set in Kafka, kafkamanager would not be able to collect the metrics. Possibly a bug in kafkamanager? |
Kafkamanager reads jmx_port from Zookeeper. Kafka sets this variable in ZK only when JMX_PORT environment variable was exported before starting Kafka. |
I see what you mean. Source the service.conf file is not enough. We have to explicitly export JMX_PORT, so kafka starting script will recognize it. We could make a fix to kafka image entrypoint.sh to export JMX_PORT, and rebuild the image. Will make a fix. |
Exporting JMX_PORT environment var (fix for cloudstax#70)
It shows -1 instead:
![image](https://user-images.githubusercontent.com/2444175/44218783-1d599d00-a183-11e8-9a18-8f6ec00dd86b.png)
To fix that, the environment variable JMX_PORT has to be set before starting Kafka.
Please, add it to the Kafka task definition.
Probably the line should be:
The text was updated successfully, but these errors were encountered: