-
Notifications
You must be signed in to change notification settings - Fork 280
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
Deploy model causes docker container to exit #149
Comments
Confirming that I can reproduce this. I was able to reproduce the error while running under lldb. Attaching the stacktrace here for future reference.
And the full log:
|
We have also noticed when is a model is being deployed (ie when a docker container is pulled), the output of Actually clipper currently cant handle multiple projects. |
I've found the issue. I'll be submitting a fix in a few minutes. |
Let me pull that statement back a little bit. I've found the problem that causes the query_frontend container to die when a new model is deployed. It may be related to #148 as well (where Clipper can't handle to applications), but I have yet to verify that. I will look into that next. As far as the problem where Clipper returns default when a new model is deployed but the container hasn't connect yet, this is a separate issue. It's not exactly a bug, just less than desirable behavior. I'm going to file a separate issue that explains the problem. |
Filed #152 to track the default predictions issue |
Thank you for the clarifications. Clearer now :) |
To reproduce this
/predict
api to do a simple call/predict
query_frontend container exits with code 139
This is the container log before exiting
Is there any other log i can look at whats happening. I am using the NoopContainer
The text was updated successfully, but these errors were encountered: