UNAVAILABLE: LDS resource does not exist

[zxyao145]

Hi，there are two pods in my deployment, and everything is normal after rolling releases. But after a period of time(hours or days), the last released pod always prompts: UNAVAILABLE: LDS resource does not exist:

UNAVAILABLE: LDS resource does not exist: <service-name>
io.grpc.StatusRuntimeException: UNAVAILABLE: LDS resource does not exist: miot.business.datacenter.server-poc
        at io.grpc.stub.ClientCalls.toStatusRuntimeException(ClientCalls.java:275) ~[grpc-stub-1.57.0-xds1.0.0.jar!/:1.57.0-xds1.0.0]
        at io.grpc.stub.ClientCalls.getUnchecked(ClientCalls.java:256) ~[grpc-stub-1.57.0-xds1.0.0.jar!/:1.57.0-xds1.0.0]
        at io.grpc.stub.ClientCalls.blockingUnaryCall(ClientCalls.java:169) ~[grpc-stub-1.57.0-xds1.0.0.jar!/:1.57.0-xds1.0.0]
        at  ........

And the other pod is normal. In the logs of XDS server, one long connection persists while the other is disconnected.

Could someone help guide us? Thanks 🙏!

Related environmental information:

• envoy：v1.24.0
• grpc-xds: 1.57.0

[ejona86]

1.57.0 is over 1.5 years old. A lot has changed in gRPC, especially xDS, since then. I'd suggest upgrading to at least 1.70.0; it fixes a regression introduced in 1.66.0 and has other fixes/improvements in the xDS communication.

[zxyao145]

Thank you for your reply! And we will try to upgrade to the version later.