Service Prediction Failed

Symptom

After a real-time service is deployed and running, an inference request is sent to the service, but the inference failed.

Cause Analysis and Solution

Service prediction involves multiple phases, including the client, Internet, APIG, dispatcher, and model service. A fault in any phase may lead to a prediction failure.

Figure 1 Prediction process

1. If an "APIG.XXXX" error occurs, the request is intercepted on API Gateway due to a fault.

   Rectify the fault by referring to Error "APIG.XXXX" Occurred in a Prediction Failure.

   The following shows the other cases in which a request is intercepted on API Gateway:

   • Method Not Allowed
   • Request Timed Out
2. If a "ModelArts.XXXXX" error occurs, the request is intercepted on the dispatcher due to a fault.

   Rectify the fault by referring to the methods provided in the following typical cases:

   • Error ModelArts.4302 Occurred in Real-Time Service Prediction
   • Error ModelArts.4302 Occurred in Real-Time Service Prediction
   • Error ModelArts.4503 Occurred in Real-Time Service Prediction
3. If an inference image is used and an "MR.XXXX" error occurs, the request has been sent to the model service, and the fault is generally due to a bug in model inference code.

   Identify the cause of the prediction failure based on the error information in logs, debug the model inference code, and import the model again for prediction.

   Rectify the fault by referring to Error MR.0105 Occurred in Real-Time Service Prediction.

4. In other cases, check whether the client and the Internet are accessible.
5. If the fault persists, contact the system administrator.