envoyproxy/envoy

warming listener never goes to active state

Open

#25,907 opened on Mar 3, 2023

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/xdshelp wantedquestion

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

I use istiod(1.10) as the control plane to configure envoy (1.18.4). There is a listener 0.0.0.0:8443. There are several filter chain which use server_name as the filter match in the same listener. Someday, after istiod push a new filter chain in listener 0.0.0.0:8443, the listener becomes warming state and never goes to active state again. I enable the debug log and see that envoy has received the rds done message and notify Listener-local-init-manager. But Listener-local-init-manager never notify Listener-local-init-watchers so that inPlaceFilterChainUpdate is never called to move the warming state to active.

023-03-03T06:46:42.612580Z debug envoy init init manager Listener-local-init-manager 0.0.0.0_8443 7610276401637039573 initializing shared target RdsRouteConfigSubscription init https.443.bozhangtest10cont-https-443.bozhangtest10cont.bozhangtest1-pre-production-1 2023-03-03T06:46:42.612584Z debug envoy init shared target RdsRouteConfigSubscription init https.443.bozhangtest10cont-https-443.bozhangtest10cont.bozhangtest1-pre-production-1 initialized, notifying init manager Listener-local-init-manager 0.0.0.0_8443 7610276401637039573

Contributor guide