[xDS] send eDS request directly if ClusterName is already known

38 views
Skip to first unread message

echo...@gmail.com

unread,
Aug 13, 2020, 2:29:17 AM8/13/20
to grpc.io
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

Yi-Shu Tai

unread,
Aug 14, 2020, 12:02:12 PM8/14/20
to grpc.io
so the easiest way is implement the missing lDS, cDS endpoint

--
You received this message because you are subscribed to a topic in the Google Groups "grpc.io" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/grpc-io/RDAJ-ypbtqA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to grpc-io+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/25434b7a-b704-4775-a8a4-62e51a6e48d1n%40googlegroups.com.


--
戴翊書
Yi-Shu Tai
Software Engineer @Dropbox

Easwar Swaminathan

unread,
Aug 19, 2020, 1:18:49 PM8/19/20
to grpc.io
You should be able to directly use the EDS LB policy without having to use the LDS/RDS/CDS. Could you give us more info on your setup? And maybe file a question (or issue) in the language specific gRPC repo that you are using?

Thanks
Easwar

Yi-Shu Tai

unread,
Aug 20, 2020, 12:33:28 AM8/20/20
to Easwar Swaminathan, grpc.io
Hi Easwar,

Thanks for the reply. Sorry I should be clear that I am using the grpc c++ client.

You should be able to directly use the EDS LB policy without having to use the LDS/RDS/CDS.
Yes.  But the grpc client first issues a LDS request and waits for 15s timeout before sending eDS request. my question is is there a way around this 15s timeout? 
I thought for a bit it's hard to tell if the endpoint does not implement LDS or it's just very slow. Unless these are some options I missed in the service config or xDS bootstrap file.

In the end, I found it's easier to implement LDS, CDS.

Best,
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 grpc-io+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/4093703a-3fb6-48be-9cd5-57b901ac4f76n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages