Increase gateway retry interval, retry max, and request timeouts#233
Merged
jinnthehuman merged 2 commits intoGoogleCloudDataproc:mainfrom Mar 19, 2025
Merged
Conversation
Serverless instances can take more than 5 minutes to start up so when jupyter server attempts to connect to the kernel, the default gateway interval and max can cause it to timeout and drop messages. Batch creation is done via a POST request and can take up to 10 minutes to be created (POST response is returned). This change increases that request timeout to be 10 minutes. All of these values are treated as minimums and will be set if and only if the config setting is not set or the config setting is less than the min value.
jinnthehuman
force-pushed
the
addGatewayConfigChanges
branch
from
498782e to
f338a0e
Compare
ptch314
approved these changes
Mar 19, 2025
ojarjur
approved these changes
Mar 19, 2025
saranyaloganathan23
pushed a commit
to Shubha-accenture/dataproc-jupyter-plugin-fork
that referenced
this pull request
Apr 28, 2025
…gleCloudDataproc#233) * Increase gateway retry interval, retry max, and request timeouts Serverless instances can take more than 5 minutes to start up so when jupyter server attempts to connect to the kernel, the default gateway interval and max can cause it to timeout and drop messages. Batch creation is done via a POST request and can take up to 10 minutes to be created (POST response is returned). This change increases that request timeout to be 10 minutes. All of these values are treated as minimums and will be set if and only if the config setting is not set or the config setting is less than the min value. * Update the set action to be more pythonic
amatheen
pushed a commit
to Shubha-accenture/dataproc-jupyter-plugin-fork
that referenced
this pull request
Apr 28, 2025
…gleCloudDataproc#233) * Increase gateway retry interval, retry max, and request timeouts Serverless instances can take more than 5 minutes to start up so when jupyter server attempts to connect to the kernel, the default gateway interval and max can cause it to timeout and drop messages. Batch creation is done via a POST request and can take up to 10 minutes to be created (POST response is returned). This change increases that request timeout to be 10 minutes. All of these values are treated as minimums and will be set if and only if the config setting is not set or the config setting is less than the min value. * Update the set action to be more pythonic
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
3 participants
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.
Serverless instances can take more than 5 minutes to start up so when jupyter server attempts to connect to the kernel, the default gateway interval and max can cause it to timeout and drop messages.
Batch creation is done via a POST request and can take up to 10 minutes to be created (POST response is returned). This change increases that request timeout to be 10 minutes.
All of these values are treated as minimums and will be set if and only if the config setting is not set or the config setting is less than the min value.