You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When should the client expect to see a value of SHUTDOWN when watching the channel's state changes?
I've noticed an unexpected behavior where the client prints out the state changes of the connection, when the server is attempting to gracefully shutdown. The client will see IDLE, CONNECTING, and then TRANSIENT_FAILURE after the server has initiated a graceful shutdown.
To reproduce the behavior, I've setup a simple server and client with a bidirectional stream between them. After the RPC is opened, the server will call shutdown() and the client's runnable will print out the state changes. I was hoping to see SHUTDOWN as one of the states, but that appears to only occur when the client initiates a shutdown on the channel, not the server.
The text was updated successfully, but these errors were encountered:
gRPC version: v1.68.1
When should the client expect to see a value of SHUTDOWN when watching the channel's state changes?
I've noticed an unexpected behavior where the client prints out the state changes of the connection, when the server is attempting to gracefully shutdown. The client will see IDLE, CONNECTING, and then TRANSIENT_FAILURE after the server has initiated a graceful shutdown.
To reproduce the behavior, I've setup a simple server and client with a bidirectional stream between them. After the RPC is opened, the server will call shutdown() and the client's runnable will print out the state changes. I was hoping to see SHUTDOWN as one of the states, but that appears to only occur when the client initiates a shutdown on the channel, not the server.
The text was updated successfully, but these errors were encountered: