Hi, Previous discussion here - https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/grpc-io/qOJaIoIzAu0/jdN9VYFLAAAJ
It seems like there is a discrepancy in the way grpc shutdown API works between Java and C++. From Java docs, shutdown() Initiates an orderly shutdown in which preexisting calls continue but new calls are rejected. shutdownNow() Initiates a forceful shutdown in which preexisting and new calls are rejected. The Java shutdown call looks non-blocking from the documentation. Looking at C++ implementation, it looks like when the shutdown call is invoked without specifying the deadline, it blocks until all the work is done. When deadline is specified, the pending work will be cancelled after deadline. The blocking nature of the Shutdown api makes it hard to initiate shutdown sequence. Is it possible to add an api that simply stops new incoming work in a non-blocking fashion (like Java shutdown API)? The application can then process pending rpcs in a graceful manner and just block when necessary. Thanks. -- 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/b7fbf014-e803-4df9-b8f0-fd09b72bbd5e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
