Skip to content

Conversation

@shs96c
Copy link
Collaborator

@shs96c shs96c commented Sep 29, 2025

The hang happened at shutdown because the server called System.exit(0) without replying to the Lifecycle.Shutdown RPC. The gRPC server then waited up to 30s with an in-flight call. Closing the client socket immediately would produce a (benign) “Broken pipe” GOAWAY stacktrace.

This change results in far faster shutdown of the gRPC server.

Copy link
Collaborator

@illicitonion illicitonion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉

The hang happened at shutdown because the server called `System.exit(0)`
without replying to the `Lifecycle.Shutdown` RPC. The gRPC server then
waited up to 30s with an in-flight call. Closing the client socket
immediately would produce a (benign) “Broken pipe” GOAWAY stacktrace.

This change results in far faster shutdown of the gRPC server.
@shs96c shs96c force-pushed the gazelle-fast-shutdown branch from 95b14ae to aefb867 Compare October 6, 2025 11:08
@shs96c shs96c enabled auto-merge (squash) October 6, 2025 11:13
@shs96c shs96c merged commit 2a6e670 into bazel-contrib:main Oct 6, 2025
7 of 8 checks passed
@shs96c shs96c deleted the gazelle-fast-shutdown branch October 6, 2025 11:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants