The only possible workaround right now is to make the name server a separate application with own process id. Then, it does not use the shared GRPC thread pool and is not getting stuck. That's ok for progressing in development, but not a viable final solution.
-- 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. 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/dbc97241-ceea-499e-9784-d1a2dc0463c9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
