gRPC does not use DNS TTLs. However, it does re-resolve when the connection to the server is closed, so you can use server-side connection management <https://github.com/grpc/proposal/blob/master/A9-server-side-conn-mgt.md> to have the server periodically close the connection to force the client to re-resolve.
On Monday, May 4, 2020 at 11:28:25 AM UTC-7 [email protected] wrote: > I have an application that uses go-grpc as transport and I'm wondering if > this supports dns-based failover. > > I have app1 which speaks to app2 on the dns record app2.example.com. > Under normal circumstances these connections are very long lived - weeks. > I'm wondering if there is handling in the grpc library such that when a DNS > record content changes at TTL expiration, are reconnections triggered? > > > That is, if app2.example.com changes from 1.1.1.1 to 2.2.2.2, will I see > that all connections by app1 will be reset to the new app2 address once the > TTL expires? > > I've been looking around the docs a bit but I haven't seen anything that > necessarily covers this scenario > -- 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/01640e2f-c68d-4fe4-b185-925747561bb8%40googlegroups.com.
