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 upDNS resolution happens only on startup #1683
Comments
This comment has been minimized.
This comment has been minimized.
|
Can you try starting DNS first? We use DNS SD a lot and don't hit this. The
only difference I see is DNS being unavailable at startup, so the bug might
be triggered by that condition. What I would expect in that case is that
subsequent updates properly reflected.
|
This comment has been minimized.
This comment has been minimized.
|
Thanks a lot for the quick reply. |
This comment has been minimized.
This comment has been minimized.
|
OK, it seems like it doesn't reproduce with 0.19.1. I'm closing the issue and I'll report if it happens again. Thanks! |
alon-argus
closed this
May 28, 2016
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
alon-argus commentedMay 28, 2016
Hi again everyone.
I use a DNS service for my services (specifically Mesos-DNS, but it can be Consul or any other), therefore I use Prometheus'
dns_sd_configsconfiguration option to give my services addressesThe problem is:
Prometheus resolves the SRV DNS addresses only on its startup ,so if Prometheus starts before the DNS server, it won't show all of these Targets. They won't even appear as "Down", but they'll just never appear until I'll restart Prometheus.
Version: 0.18.0