You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of Nuclio.
Issue Description
I have used nuclio with cvat for auto annotation. My use case needs a long run time for larger image passing through the inference model (the deployed nuclio function). The small test runs fine, but larger test got following errors: HTTPConnectionPool(host='host.docker.internal', port=32768): Read timed out. (read timeout=120).
As suggested by issue: #2864, there is no effect in passing parameter readinessTimeoutSeconds through function.yaml. So I have cloned tag 1.9.5 and have hard coded the const DefaultFunctionReadinessTimeoutSeconds = 120 under pkg/platformconfig/types.go to 1200. Then I rebuild nuctl and images thanks to the steps in #927. The image build and function deploy are all fine.
Finally, at the end of the
nuctl deploy --project-name cvat --path "./serverless/pytorch/my-function/nuclio/" --platform local
log, I have
although the value of readinessTimeoutSeconds is 1200, my function still halts after 120s and I received the same error of HTTPConnectionPool as before.
Expected Behavior
My function should not halt given that readinessTimeoutSeconds
The text was updated successfully, but these errors were encountered:
eatgreen
changed the title
[Bug]: changing DefaultFunctionReadinessTimeoutSeconds value and rebuild nuctl has no effect with platform local
[Bug]: changing DefaultFunctionReadinessTimeoutSeconds value and rebuild nuclio has no effect with platform local
Jun 9, 2023
Nuclio Version checks
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of Nuclio.
Issue Description
I have used nuclio with cvat for auto annotation. My use case needs a long run time for larger image passing through the inference model (the deployed nuclio function). The small test runs fine, but larger test got following errors:
HTTPConnectionPool(host='host.docker.internal', port=32768): Read timed out. (read timeout=120)
.As suggested by issue: #2864, there is no effect in passing parameter readinessTimeoutSeconds through function.yaml. So I have cloned tag 1.9.5 and have hard coded the
const DefaultFunctionReadinessTimeoutSeconds = 120
underpkg/platformconfig/types.go
to 1200. Then I rebuild nuctl and images thanks to the steps in #927. The image build and function deploy are all fine.Finally, at the end of the
nuctl deploy --project-name cvat --path "./serverless/pytorch/my-function/nuclio/" --platform local
log, I have
...platform":{"attributes":{"mountMode":"volume","restartPolicy":{"maximumRetryCount":3,"name":"always"}}},"readinessTimeoutSeconds":1200,"securityContext":{},"eventTimeout":"2000s"}}}}
although the value of readinessTimeoutSeconds is 1200, my function still halts after 120s and I received the same error of HTTPConnectionPool as before.
Expected Behavior
My function should not halt given that readinessTimeoutSeconds
Deployment Method
Docker
Nuclio Version
1.9.5
Additional Information
My function.yaml
Thanks!
The text was updated successfully, but these errors were encountered: