envoyproxy / envoyproxy/envoy

Incorrect listener readiness reporting

Open
#12,245 4 comments 0 reactions 0 assignees View on GitHub
area/docs help wanted
Dominant language
C++
Stars
28.9k
Forks
5.6k
Avg merge
1d 20h
Merged PRs (30d)
437

Description

In the process of debugging #11826 , I found that the usual stats for readiness are mis-leading. It can happen that the initial init manager finishes initializing (LDS/CDS accepted, processed, and active), yet the connections will be refused. This is because there is a delay between when init manager finishes and the workers start accepting traffic. I think this is a problem, since it may lead to pre-mature deployment of a proxy before it is ready to serve traffic.

cc @lambdai

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.