Status Update
Comments
bi...@google.com <bi...@google.com>
ej...@gmail.com <ej...@gmail.com> #2
bi...@google.com <bi...@google.com> #3
Thank you for the input. It has been forwarded to the engineering team. Note, that there are no ETAs or guarantees of implementation but I'll let you know as soon as I get any updates.
mk...@google.com <mk...@google.com> #4
Hello,
Thank you for the contributing. In order to perform a deeper investigation we would require some additional information about your current environment, like Project ID, Model ID and Version ID. For that purpose I've been requested this information in the Private issue form
ej...@gmail.com <ej...@gmail.com> #6
I provided the project id, model id and version id in #176056981. What other information do you require?
Thanks
ma...@google.com <ma...@google.com> #7
Hi,
Thank you. I will give this information for the engineering team. Please follow this thread for any updates.
jm...@google.com <jm...@google.com> #8
Thank you for your continued patience.
After further investigations, preliminary evidence suggests that users who deployed their first model within the last several months (November) and are deploying mls1* models are likely affected by this issue.
- Users who activated the AI Platform API prior to November (approximately) may be unaffected.
=> While the AI Platform engineering team works on rolling out a fix, in the meantime as workaround you are recommended to use n1* machine types [1] via regional endpoints [2] instead of mls1* machines when deploying your version to mitigate the issue.
[1]
[2]
va...@google.com <va...@google.com>
va...@google.com <va...@google.com> #9
Hello,
This issue is now fixed. In case the issue persists on your side or you want to report a new issue, please do not hesitate to create a new Issue tracker thread describing your situation. Thank you for your trust and continued support to improve Google Cloud Platform products.
Description
When deploying a custom predictor on ai-platform I get the following error
The logs show
I'm using the following command to deploy
All the environment variables have the correct values.
The deploy works without a custom prediction on a
n1-standard-4
instance inus-central1
. The custom predictor is deployed globally on amls1-c4-m2
but my bucket is still onus-central1
. I tried to deploy the custom predictor onus-central1
butn1-standard-4
doesn't support custom predictors andus-central1
doesn't havemls1-c4-m2
instances.My barebones predictor is as follows
Any help would be appreciated. I'm struggling to debug the internal error messages.