envoyproxy/envoy

feature request: add cluster intialization status to admin `/init_dump`

Open

#15.178 aberto em 24 de fev. de 2021

Ver no GitHub
 (4 comments) (0 reactions) (0 assignees)C++ (5.373 forks)batch import
area/adminhelp wanted

Métricas do repositório

Stars
 (27.997 stars)
Métricas de merge de PR
 (Mesclagem média 8d) (378 fundiu PRs em 30d)

Description

We can now query the active cluster and warm cluster to know what clusters are able to use. It's adequate to explain why a request is "NR 503", but it's still hard to troubleshooting why a cluster stays warming up.

We can expose the per cluster init::manager to cluster manager and query init manager's unready target.

The followings are need to be resolved.

  1. The cluster ready details query should be exposed to admin interface /init_dump
  2. Not all the blocking items are under the frame of init::manager. If each of the blocking item attaches to a init::target with a meaningful name, the init status can be as simple as listing all the unready target names. The current cluster initialization does not end with init::manager announce "ready".

Thoughts?

Guia do colaborador