Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upZookeeper discovery has an exception #4668
Comments
simonpasquier
added
kind/bug
component/service discovery
labels
Sep 28, 2018
This comment has been minimized.
This comment has been minimized.
|
I thought I found my problem. |
wenfei3
closed this
Sep 28, 2018
This comment has been minimized.
This comment has been minimized.
|
Reopening as there's indeed a problem with the Zookeeper SD when it can't connect to the servers. |
simonpasquier
reopened this
Sep 28, 2018
This comment has been minimized.
This comment has been minimized.
|
@simonpasquier Here is my prometheus log about ZK connection success
and here is the service in ZK
and here is my prom ui I have no idea that why the host is empty and the port is 0. |
This comment has been minimized.
This comment has been minimized.
|
Unfortunately I'm not a ZooKeeper SD expert. Which system does provision the serversets in your ZooKeeper cluster? |
This comment has been minimized.
This comment has been minimized.
|
Thanks for your reply! |
This comment has been minimized.
This comment has been minimized.
|
Closed by #4669 |

wenfei3 commentedSep 28, 2018
•
edited
Bug Report
What did you do?
Added a serverset_sd_configs job in prometheus.yml and reloaded the prometheus.
What did you expect to see?
I would expect to see the prometheus could read the services which were registerd to zookeeper cluster.
What did you see instead? Under which circumstances?
When I reloaded the prometheus.yml, the prometheus stopped working and I found some error logs.
System information:
Linux 2.6.32-573.22.1.el6.x86_64 x86_64
Prometheus version:
prometheus, version 2.3.2 (branch: HEAD, revision: 71af5e2)
build user: root@5258e0bd9cc1
build date: 20180712-14:02:52
go version: go1.10.3
Zookeeper version:
3.4.12
Prometheus configuration file: