envoyproxy/envoy

Are the lb_policy and lb_config forced to match?

Open

#25.583 aberto em 15 de fev. de 2023

Ver no GitHub
 (9 comments) (0 reactions) (0 assignees)C++ (5.373 forks)batch import
area/configurationarea/load balancinghelp wantedquestion

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

Description: Currently in clusterInfoImpl when the lb_configs are loaded, it doesn't check if the lb_policy matches the config that's loaded. We have a separate member for the lb_policy and other members for each config type. Is there anything to stop the user from setting a round_robin config but also setting the lb_policy to least request? If there isn't, should anything be done about that?

Relevant Links: Current implementation of how the lb config members are initialized

Current location of where lb_policy is set

Guia do colaborador