[grpc-io] Re: gRPC Python DNS Resolution

2019-01-25 Thread 'Srini Polavarapu' via grpc.io
>From your description it looks like you are destroying all the old servers and bringing up a completely new set of servers with new IPs. The gRPC client is still seeing old IPs in the cached DNS, none of which are available. It will try to connect to these unavailable IPs until the deadline is

[grpc-io] Re: AppEngine executor and interceptors

2019-01-25 Thread arunachalam . t
Eric Andreson helped me identify the issue. AppEngine Request thread can only be started from an another request thread. Netty Pool when it tries to start, AppEngine fails the thread creation causing the request to hang. Prestarting the thread pool fixes the problem. On Thursday, January 24, 20

[grpc-io] Re: AppEngine executor and interceptors

2019-01-25 Thread arunachalam . t
I opened this issue, https://github.com/grpc/grpc-java/issues/5286 which is the underlying problem in my opinion. On Thursday, January 24, 2019 at 11:14:01 AM UTC-8, arunac...@gmail.com wrote: > > I am trying to prototype a java client cache interceptor in AppEngine > (java8) and gRPC(1.17.1).