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
During the store initialisation process neither grpc or http server aren't running. Hence there isn't any approach to use liveness k8s probe to check if container in pod is running.
thanos, version 0.1.0-rc.2 (branch: master, revision: a4128358e9df68170a4df7f0d4c7bef2bab2c3ca)
build user: circleci@36ffc8669a55
build date: 20180718-06:16:19
go version: go1.10.3
What you expected to happen
Easy way is to run http server with a metrics endpoint (and debug) before an initialisation process. So k8s can use rollingUpdate properly with liveness and readiness probes
Initialization is a lingering process and can take minutes to sync meta and index files. Move it to background goroutine to allow metrics/debug handlers be ready right after application is start. It provides admins set up liveness and readindess probes at the k8s.
Recommendations: use http port for liveness and grpc for readyness
Fixedthanos-io#532
During the store initialisation process neither grpc or http server aren't running. Hence there isn't any approach to use liveness k8s probe to check if container in pod is running.
What you expected to happen
Easy way is to run http server with a metrics endpoint (and debug) before an initialisation process. So k8s can use rollingUpdate properly with liveness and readiness probes
https://github.com/improbable-eng/thanos/blob/master/cmd/thanos/store.go#L178
Full logs to relevant components
The text was updated successfully, but these errors were encountered: