Channels
announcements
ask-marvin
best-practices-coordination-plane
data-ecosystem
data-tricks-and-tips
events
find-a-prefect-job
geo-bay-area
geo-berlin
geo-boston
geo-chicago
geo-colorado
geo-dc
geo-israel
geo-japan
geo-london
geo-nyc
geo-seattle
geo-texas
gratitude
introductions
marvin-in-the-wild
pacc-clearcover-june-12-2023
pacc-may-31-2023
ppcc-may-16-2023
prefect-ai
prefect-aws
prefect-azure
prefect-cloud
prefect-community
prefect-contributors
prefect-dbt
prefect-docker
prefect-gcp
prefect-getting-started
prefect-integrations
prefect-kubernetes
prefect-recipes
prefect-server
prefect-ui
random
show-us-what-you-got
Title
f
Fabrice Toussaint
05/05/2021, 8:24 AMHey everyone,
Can someone explain to me why I keep getting this error in my flow runs
requests.exceptions.ReadTimeout: HTTPConnectionPool(host='prefect-apollo.prefect', port=4200): Read timed out. (read timeout=15)k
Kevin Kho
05/05/2021, 1:44 PMHey @Fabrice Toussaint, can you try increasing the timeout limit with setting the config like shown here.
f
Fabrice Toussaint
05/05/2021, 1:47 PM@Kevin Kho thank you for your reply. I see that this is only for Prefect Cloud or do I see that wrong?
k
Kevin Kho
05/05/2021, 1:48 PMI think this will work for server. I’m not 100% sure though if the config is
prefect.context.config.cloud.request_timeoutprefect.context.config.server.request_timeoutI asked the team and I’ll update you when I get a response. You can try both though.
f
Fabrice Toussaint
05/05/2021, 1:48 PMI will check it out, thanks again 😄!
k
Kevin Kho
05/05/2021, 1:49 PMTo answer your question, it’s really a read time out when you hit the API. The connection is good. Do you have a big Flow?
f
Fabrice Toussaint
05/05/2021, 1:50 PMYes the flow can be quite big, so that makes sense actually
k
Kevin Kho
05/05/2021, 2:19 PMConfirmed that you still use
config.cloudf
Fabrice Toussaint
05/05/2021, 2:20 PM`config.cloud`instead of
server.cloudk
Kevin Kho
05/05/2021, 2:20 PMYes
prefect.context.config.cloud.request_timeoutf
Fabrice Toussaint
05/05/2021, 2:21 PMI have prefect deployed using Kubernetes with the Helm chart, can I just set it in the job_template.yaml as an environment variable?
--> PREFECT_CONTEXT_CONFIG_CLOUD_REQUEST_TIMEOUT = ...
or just in the flow itself
k
Kevin Kho
05/05/2021, 2:25 PMLet me confirm the syntax
PREFECT__CONTEXT__CONFIG__CLOUD__REQUEST_TIMEOUTf
Fabrice Toussaint
05/05/2021, 2:27 PMthank you 😄
gives me an error
k
Kevin Kho
05/05/2021, 2:47 PMOk let me find a way to edit it on the flow side
Actually I don’t think we can because context is read only when the flow starts. Let me ask someone.
f
Fabrice Toussaint
05/05/2021, 2:49 PMThanks again 😄
k
Kevin Kho
05/05/2021, 2:55 PMI think this is your issue. You can use a custom job template, or maybe you can try passing the env var upon agent start
f
Fabrice Toussaint
05/05/2021, 2:56 PMI am using a custom job template for my agent
k
Kevin Kho
05/05/2021, 2:56 PMprefect agent kubernetes start --env KEY=VALUEI see let me look into it more
f
Fabrice Toussaint
05/05/2021, 2:57 PMI can set other environment variables and they work just fine
example
k
Kevin Kho
05/05/2021, 3:06 PMUse “60” for the value. It will be converted
f
Fabrice Toussaint
05/05/2021, 3:07 PMMy bad 😂
Thank you
a
Adam Lewis
05/06/2021, 8:59 PMI'm having this same issue today. I've deployed prefect server on kubernetes as well. Do y'all know if I can set this value in the config.toml? I'm not sure if setting it in the toml file would quite make it's way to the prefect context or not.
k
Kevin Kho
05/06/2021, 9:02 PMYes you can with
prefect.context.config.cloud.request_timeouta
Adam Lewis
05/06/2021, 9:03 PMYou're saying I should run
prefect.context.config.cloud.request_timeout=60k
Kevin Kho
05/06/2021, 9:04 PMI was thinking in the toml under [context] -> [config] -> [cloud]
request_timeout
a
Adam Lewis
05/06/2021, 9:04 PMAnd then I'd need to reregister the flows for the setting to take effect, is that right?
k
Kevin Kho
05/06/2021, 9:24 PMThat sounds right
🙌 1