Hey does this just mean our EKS cluster hasn’t whi...
# ask-communityd
Dylan
05/09/2022, 3:40 PMHey does this just mean our EKS cluster hasn’t whitelisted api.prefect.io?
Dylan
05/09/2022, 3:40 PM Copy code
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='<http://api.prefect.io|api.prefect.io>', port=443): Max retries exceeded with url: / (Caused by ReadTimeoutError("HTTPSConnectionPool(host='<http://api.prefect.io|api.prefect.io>', port=443): Read timed out. (read timeout=15)"))k
Kevin Kho
05/09/2022, 3:42 PM
No it could be you have a big API call happening. You can increase that like by setting
Copy code
prefect.context.config.cloud.request_timeoutd
Dylan
05/09/2022, 3:50 PMWhat’s the surface and size of the API calls?
Dylan
05/09/2022, 3:53 PMAnd is there an environment variable for that setting? we’re running a prefect cloud agent so I’m not using that config.toml
Dylan
05/09/2022, 3:54 PMLooking here for reference
k
Kevin Kho
05/09/2022, 3:56 PM
Should be
Copy code
PREFECT__CLOUD__REQUEST_TIMEOUTcreate_flow_rund
Dylan
05/09/2022, 4:00 PMI don’t have any tasks that create their own flows, pretty simple so far, flow registration runs separately from flow execution, flows executing are simple tasks (not composing tasks from or within tasks for example) but I am passing state between tasks. Would it be possible that this is an error masking an underlying connection error for a failed
prefect.engine.results.S3Resultk
Kevin Kho
05/09/2022, 4:02 PM
I don’t think so because that would use the boto3 client. I think this is specifically the Prefect Client. Was this a one time thing yesterday?
Kevin Kho
05/09/2022, 4:03 PM
There was a spike in latency but I don’t think it was an incident. Or does this happen with some regularity?
d
Dylan
05/09/2022, 4:09 PMSeems to just be once occurrence on 5/7
k
Kevin Kho
05/09/2022, 4:42 PM
There may have been increased latency on 5/7 6pm ET so it might be a one off thing also
56 Views