ORC-2108: Add connection timeout to JIRA client to prevent hanging and enable retries#2552
Closed
dongjoon-hyun wants to merge 1 commit intoapache:mainfrom
Closed
ORC-2108: Add connection timeout to JIRA client to prevent hanging and enable retries#2552dongjoon-hyun wants to merge 1 commit intoapache:mainfrom
dongjoon-hyun wants to merge 1 commit intoapache:mainfrom
Conversation
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
1 participant
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.
What changes were proposed in this pull request?
This PR aims to add a generic connection and read timeout parameter timeout=(3.05, 30) to the
jira.client.JIRA()initializations in the dev/ scripts:create_orc_jira.pymerge_orc_pr.pyWhy are the changes needed?
By default, the requests library (used by the jira python package) can hang indefinitely when attempting to establish a connection if the server is unresponsive. Setting a short connection timeout of 3.05 seconds (slightly larger than a standard 3-second TCP packet retransmission window) ensures that the client will quickly fail the connection attempt and properly trigger its internal retry logic, rather than stalling the entire script. The 30-second read timeout allows sufficient time for normal API responses once the connection is successfully established.
How was this patch tested?
Manual tests.
Was this patch authored or co-authored using generative AI tooling?
Generated-by:
Gemini 3.1 Pro (High)onAntigravity