envoyproxy/envoy
GitHub で見る503 + NR due to the inconsistency between the order in which the configuration takes effect and the order in xDS push
Open
#13,910 opened on 2020年11月5日
area/xdsbughelp wanted
Repository metrics
- Stars
- (27,997 stars)
- PR merge metrics
- (平均マージ 8d) (30d で 378 merged PRs)
説明
We currently use a control plane software to dynamically create clusters and routes. However, in practice, we have found that if we create a route immediately after creating a cluster. For a very small period of time, requests to access the route return 503 + NR.
We speculate that the process of cluster warming causes the cluster configuration to take effect later than the route configuration takes effect. But not for sure.
I wonder if the community has encountered a similar problem? Any suggestions?