-
Notifications
You must be signed in to change notification settings - Fork 834
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
initialDelaySeconds: 10 sec is not enough for some models #323
Comments
Have you tried adding your own liveness and readiness probes in the podTemplateSpec? It should only add the default ones if ones don't exist already. |
Do you mean to add it to the prototype? Now I tried this:
Then, "kubectl get seldondeployment ... -o json " returns: The deployment does not show up actually in K8s. Maybe I am missing here something. This is the full prototype file I used with the probes added:
|
You need to specify the tcpSocket more explicitly. We use the Kubernetes Proto Buffer definitions for parsing which are more strict than that allowed by the OpenAPI versions. Try something like:
|
Wow, this helped :) |
I have a model which is loading bigger amount of data (it takes around 45 sec in the init() ), deploying it with Kubeflow, seldon-serve-simple-v1alpha2.
The liveness and readiness probes timeout, and the container gets cyclically restarted, never getting initialized.
When I manually increase the initialDelaySeconds values for both probes in the K8s deployment, the pod gets initialized successfully. I tried this via the K8s dashboard by clicking Edit on the model deployment.
What is the proper way to increase these delay values?
I can see that the 10 seconds seems to be hardcoded in SeldonDeploymentOperatorImpl.java, but can I somehow change this when generating the SeldonDeployment with Kubeflow?
I guess this can affect several models where the initialization involves loading large amount of data.
The text was updated successfully, but these errors were encountered: