Reduce default agent ping interval to 30s to avoid idle timeouts - #26448
Closed
abhay1999 wants to merge 1 commit into
Closed
Reduce default agent ping interval to 30s to avoid idle timeouts#26448abhay1999 wants to merge 1 commit into
abhay1999 wants to merge 1 commit into
Conversation
Made-with: Cursor
Contributor
|
Missing required label for changelog. Requires at least 1 of: bug, developer, dependencies, internal, localization, major-bug, major-rfe, rfe, regression-fix, removed, skip-changelog. Found: spam. You can add the required label by adding a comment with the following text: |
Contributor
|
Why do you open a new PR when there is already an identical PR open? |
Member
Member
Contributor
On plugins I usually mark them as spam. |
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.

Summary
This PR reduces the default TCP agent ping interval from 5 minutes to 30 seconds in .
Modern Jenkins installations frequently run behind load balancers and reverse proxies (such as AWS NLB + nginx-ingress) that use relatively short idle timeouts (around 60 seconds). With the existing 5-minute default, there can be long idle periods with no traffic, during which intermediaries terminate the TCP connection. The next scheduled then sees a and the server continues to believe the agent is already connected for several minutes, leading to repeated logs and temporarily unavailable agents.
Aligning the default TCP ping interval with the websocket ping behavior (30s) keeps traffic flowing frequently enough to avoid these idle timeouts by default, without requiring manual system property tuning.
This change is motivated by and intended to address #26338 and is consistent with the proposal in #26353.
Details
Testing
Credits
Authored by @abhay1999 for improving robustness of Jenkins agent connections in modern cloud / proxy environments.
Made with Cursor