hey folks,
We have an eDS control plane. we can create a client with service config
like
```
"loadBalancingConfig": [
{"eds_experimental": {"clusterName": xds_cluster_name}}
]
```
so that we can just get the ClusterLoadAssignment without obtaining Cluster
by LDS, RDS.
However, xDS client sends ADS sequentially and has a 15s timeout. In our
setup, the first LDS call blocked for 15s because the control plane does
not talk in LDS. It's not good to spend 15s to init a client, so can we
bypass first LDS call and send eDS if we already know the clusterName? or
is there any other way around to reduce/remove this 15s wait?
Thanks,
yishu
--
You received this message because you are subscribed to the Google Groups
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/grpc-io/25434b7a-b704-4775-a8a4-62e51a6e48d1n%40googlegroups.com.
