Open huan opened 2 years ago
I believe this behavior is expected with the Node.js server.close() callback explanation in the above issue:
The grpc.tryShutdown()
will call server.close(callback)
, however, the callback
might not be called immediately because the server.close only stop accepting new connections.
There might be other active connections left, which means the callback
will be only called after all of them have been closed.
After testing, it seems that even we have called grpc.forceShutdown()
, the promise returned from tryShutdown()
still can not be resolved.
So we have to ignore it for now and hope we can find the reason in the future.
Version:
@grpc/grpc-js@1.4.1
Related issue:
Log messages:
Source code:
https://github.com/wechaty/puppet-service/blob/a764bd22655a60117bbd118c64469feb6b16d33a/tests/grpc-stream.spec.ts#L71-L78
why-is-node-running
report