The behavior is supposed to be that we periodically (with exponential back-off) retry resolution and then connection until we get a successful connection.
We currently rely on getaddrinfo to do the resolution, so we don't get any insight into the TTL on the dns entry - that's something we'll pick up soon though (with an optional embedding of c-ares). Could you add a log line to blocking_resolve_address_impl() in resolve_address_posix.c and verify that we are in fact repeatedly calling this? On Thu, Aug 18, 2016 at 4:20 PM Abhishek Parmar <abhis...@carbon3d.com> wrote: > (Replying for Yaz, he is on vacation) > > On Thu, Aug 18, 2016 at 4:15 PM, <raute...@gmail.com> wrote: > >> Steps 4 and 5 should be interchanged I think. >> > > You mean 3 and 4 should be swapped? I don't think it matters. > > >> >> What does host foo.example.com results in, on your computer? >> >> Are you running your code on a Linux box or some other environment? >> > > It is running on linux. > > >> >> Thanks, >> >> On Wednesday, 17 August 2016 13:49:21 UTC-7, Yaz Saito wrote: >>> >>> Assume we have foo.example.com, whose value changes unpredictably. >>> >>> 1. Initially, the A record of foo.example.com points to, say 1.2.3.4. >>> 2. Start a grpc client, with the server pointed at foo.example.com:10000. >>> The client fails to >>> connect since there's nothing running at 1.2.3.4:10000. >>> 3. Start a grpc server at an IP address 1.2.3.5:10000. >>> 4. Update the DNS server so that foo.example.com points to 1.2.3.5. >>> >>> In this situation, the grpc client never seems to discover the server at >>> 1.2.3.5, even when I set the DNS TTL very short. >>> >>> Am I diagnosing the problem correct? And if so, is there a way to work >>> around? >>> >>> -- >>> yaz >>> >> -- >> 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+unsubscr...@googlegroups.com. >> To post to this group, send email to grpc-io@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/grpc-io/f20ea25a-0487-4907-adb4-59f58791aff5%40googlegroups.com >> <https://groups.google.com/d/msgid/grpc-io/f20ea25a-0487-4907-adb4-59f58791aff5%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > -Abhishek > > -- > 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+unsubscr...@googlegroups.com. > To post to this group, send email to grpc-io@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/grpc-io/CAD2hsky0%2BBYGA1s-jat%3DC4D2F37UGoGLRPKnsYGAzxFE2Ff5kA%40mail.gmail.com > <https://groups.google.com/d/msgid/grpc-io/CAD2hsky0%2BBYGA1s-jat%3DC4D2F37UGoGLRPKnsYGAzxFE2Ff5kA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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+unsubscr...@googlegroups.com. To post to this group, send email to grpc-io@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CAAvp3oP15UG4Ubo0iRJPfUWR453O0_f42NToXukqKtLQ3XC_MQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
