Google treats JVM shutdown as a more immediate action to take, while GOAWAY is not as urgent. At least in our cases, the JVM shutting down (i.e. code run from Runtime.addShutdownHook) implies that everything should be destroyed asap.
I think what you want is to shutdown the gRPC server and all connections before initiating a full jvm shutdown. That would have the desired behavior you want, and wouldn't conflate the two shutdowns. On Thursday, December 22, 2016 at 7:21:30 AM UTC-8, [email protected] wrote: > > Hello, > > When we redeploy our servers on AWS, behind an ELB we would like to > support graceful shutdown by pushing a GOAWAY frame to the already > connected clients and initiate a graceful shutdown of the clients > connection to the server. After some amount of time after the GOAWAY frame > has prompted shutdown we would like the clients to re-establish a > connection with the servers. > > I see this sort of behaviour implemented in the GO server > https://github.com/grpc/grpc-go/pull/774 > > Is this also implemented in the grpc-java server (a link to the code would > be appreciated) ? > > Also, we plan to implement a scheduled DNS name resolver for updating our > ELB DNS with the appropriate TTL > https://github.com/grpc/grpc-java/issues/2514 , will the GOAWAY frame > behaviour above effect a scheduled DNS name resolver? > > Thanks, > > Mike > -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/888fdf6d-cc67-43b2-b1dc-ad1d05cc5cf7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
