You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanos, Prometheus and Golang version used:
thanos: 0.23.1
prometheus: 2.31.1
openshift: v3.11.88
k8s: v1.11.0
Object Storage Provider: None
What happened:
when i curl http://thanos-query-pod-cluster-ip:9090/-/healthy return ok,
but curl http://thanos-query-pod-cluster-ip:9090/api/v1/query?query=up timeout.
Only one of the three pods will have this situation.
Something must be happening inside this pod, but the log can't see anything.
The configuration file is as follows
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Full logs to relevant components:
Anything else we need to know:
The text was updated successfully, but these errors were encountered:
livenessProbe url modified to /api/v1/query?query=up. When thanos-query does not work, the pod will be restarted.this is my solution, But not the best solution.
Thanos, Prometheus and Golang version used:
thanos: 0.23.1
prometheus: 2.31.1
openshift: v3.11.88
k8s: v1.11.0
Object Storage Provider: None
What happened:
when i
curl http://thanos-query-pod-cluster-ip:9090/-/healthy
return ok,but
curl http://thanos-query-pod-cluster-ip:9090/api/v1/query?query=up
timeout.Only one of the three pods will have this situation.
Something must be happening inside this pod, but the log can't see anything.
The configuration file is as follows
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Full logs to relevant components:
Anything else we need to know:
The text was updated successfully, but these errors were encountered: