Skip to content
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

Warning: "Calling MMS with mxnet-model-server. Please move to multi-model-server." #69

Open
mb-dev opened this issue Sep 11, 2020 · 2 comments

Comments

@mb-dev
Copy link

mb-dev commented Sep 11, 2020

Describe the bug
When deploying sagemaker endpoint using the example dockerfile: https://github.com/awslabs/amazon-sagemaker-examples/tree/master/advanced_functionality/multi_model_bring_your_own we now get the above warning "Calling MMS with mxnet-model-server. Please move to multi-model-server."

Seems the command here:
https://github.com/aws/sagemaker-inference-toolkit/blob/master/src/sagemaker_inference/model_server.py#L83

Should change according to:
https://github.com/awslabs/multi-model-server/blob/72e09f998874f5701404031441573e0eb6f2f866/mms/model_server.py#L20

To reproduce
See above

Expected behavior
No warning given

Screenshots or logs
If applicable, add screenshots or logs to help explain your problem.

System information
A description of your system.

  • Include the version of SageMaker Inference Toolkit you are using.
  • If you are using a prebuilt Amazon SageMaker Docker image, provide the URL.
  • If you are using a custom Docker image, provide:
    • framework name (eg. PyTorch)
    • framework version
    • Python version
    • processing unit type (ie. CPU or GPU)

Additional context
Add any other context about the problem here.

@chuyang-deng
Copy link
Contributor

chuyang-deng commented Sep 22, 2020

Hi @mb-dev, thanks for pointing this out. The model server has renamed from mxnet-model-server to multi-model-server, and we will update the command, at the same time, contribution is welcomed.

@jperuggia
Copy link

This issue is pretty stale and appeared to have been addressed. any reason it is still open?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants