Skip to content
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 "ready" when Prometheus is replaying WAL #4919

Closed
GiedriusS opened this issue Dec 2, 2021 · 1 comment
Closed

Sidecar "ready" when Prometheus is replaying WAL #4919

GiedriusS opened this issue Dec 2, 2021 · 1 comment

Comments

@GiedriusS
Copy link
Member

Thanos, Prometheus and Golang version used:

0.23.1

Object Storage Provider:

N/A

What happened:

Restarted Prometheus, it started replaying WAL. Sidecar still reported its status as "READY" via /-/ready hence it appears in Thanos Query, and then Thanos Query starts lagging unnecessarily waiting for an answer from Prometheus.

By definition, Sidecar is not ready to serve traffic if Prometheus is down.

What you expected to happen:

For Sidecar to either not report the status as READY or for Sidecar/Query not to hang waiting for an answer from Prometheus.

How to reproduce it (as minimally and precisely as possible):

  • Restart bigger Prometheus
  • Inspect Sidecar status

Full logs to relevant components:

{"caller":"sidecar.go:207","err":"expected 2xx response, got 503. Body: Service Unavailable","level":"warn","msg":"heartbeat failed","ts":"2021-12-02T11:57:36.068816651Z"}
@GiedriusS
Copy link
Member Author

Fixed in #4939.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant