Skip to content

client stuck with "StatusCode.INTERNAL, GOAWAY received" after server restarted #14088

@sammy-tam

Description

@sammy-tam

Please answer these questions before submitting your issue.

Should this be an issue in the gRPC issue tracker?

Yes

What version of gRPC and what language are you using?

1.8.4

What operating system (Linux, Windows, …) and version?

Linux, OLE 7.2

What runtime / compiler are you using (e.g. python version or version of gcc)

python 3.6.4

What did you do?

Client is calling RPC Server every second, and while its running normally, restart RPC Server process. (localhost) TWICE.

What did you expect to see?

Client be able to reconnect to server successfully.

What did you see instead?

The first restart, it will always return (Internal, Connect Failed), as expected.

Once this message is seen, restart the RPC Server again, it will return
<_Rendezvous of RPC that terminated with (StatusCode.INTERNAL, GOAWAY received)>

Once it gets to this state, it is stuck forever. I have tried all different options, including re-creating the channel and stub once this go away is received. They seem to stay this way until I restart my client process.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions