Repository navigation
Set Jetty HTTP idle timeout to 620s - #3250
Merged
Merged
Conversation
Increase jetty.http.idleTimeout from the 30s default (30000ms) to 620s (620000ms) in start.d/http.ini so that it exceeds the Google Cloud Application Load Balancer's fixed 600s backend keep-alive timeout. This prevents the HTTP/1.1 persistent connection race condition where Jetty closes an idle pooled connection at 30s while GCLB forwards a non-idempotent HTTP POST request (such as /_dr/epp, /_dr/task, /_dr/cron, /_dr/admin, or /_dr/epptool) over the same socket, resulting in 503 Service Unavailable (connection termination) drops. BUG= http://b/577105059
njshah301
force-pushed
the
fix/jetty-http-idle-timeout
branch
from
October 23, 2026 16:42
47b62b9 to
de739ca
Compare
njshah301
enabled auto-merge
October 23, 2026 16:58
gbrodman
approved these changes
Oct 23, 2026
gbrodman
left a comment
gbrodman
left a comment
Collaborator
There was a problem hiding this comment.
@gbrodman reviewed 1 file and all commit messages.
Reviewable status:complete! all files reviewed, all discussions resolved (waiting on njshah301).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Increase jetty.http.idleTimeout from the 30s default (30000ms) to 620s (620000ms) in start.d/http.ini so that it exceeds the Google Cloud Application Load Balancer's fixed 600s backend keep-alive timeout.
This prevents the HTTP/1.1 persistent connection race condition where Jetty closes an idle pooled connection at 30s while GCLB forwards a non-idempotent HTTP POST request over the same socket, resulting in 503 Service Unavailable (connection termination) drops.
Refer: GCP Load Balancing docs
BUG= b/577105059
This change is