-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
sidecar: delayed gossip startup if peer is not working #372
Comments
Hi - have you found a work around for this issue - I probably hit this a few times a day in development. |
@pharaujo / @cwolfinger I think this PR #383 should fix it, if you want you can try running my docker image (tagged master) https://hub.docker.com/r/povilasv/thanos/tags/ |
yea, @cwolfinger @pharaujo did you have a chance to try fixed Thanos docker image? BTW |
I haven't had the chance to test it out yet. @Bplotka yes, I'm running thanos query on the grafana nodes. |
Fix landed to master, so let us know if you can repro (#383) |
I was able to reproduce this today... took about 2 mins for my
I am using |
@midnightconman This is totally unrelated. We are talking about gossip startup not store gateway init. This is known to take time. Closing this then for now. |
Disable dedup proxy in multi-tsdb
Thanos, Prometheus and Golang version used
Thanos built from master.
What happened
Running thanos (sidecar in this case) with a list of 4 cluster peers, 2 of which weren't running yet. Gossip startup took more around 1 minute. Trying to connect to gossip cluster with
thanos query
before the cluster was up resulted in it not connecting at all after the cluster was set up. Restartingthanos query
after this resulted in immediate cluster membership.What you expected to happen
I expected to have the cluster be joinable, and expected the query node to join the cluster automatically after it was formed.
How to reproduce it (as minimally and precisely as possible):
Run 2 sidecars with 4 cluster peers, two of which exist but are not running any thanos component; Try to connect to the cluster with a query node.
Full logs to relevant components
Environment:
The text was updated successfully, but these errors were encountered: