Project: Vald (App Definition and Development / Database)
File: mirror-gateway.md

This page introduces the popular troubleshooting for Mirror Gateway. Additionally, if you encounter some errors when using API, the helps you, too. Mirror Gateway sends an Update request to its host if some requests are `ALREADY_EXISTS`. Therefore, in addition to the , the may also be returned to the user. Here are some common reasons of error. | name | common reason | | :- | :-- | | CANCELLED | Executed cancel() of rpc from client/server-side or network problems between client and server. | | INVALID_ARGUMENT | The Dimension of the request vector is NOT the same as Vald Agent's config, the requested vector's ID is empty, or some request payload is invalid. | | DEADLINE_EXCEEDED | The RPC timeout setting is too short on the client/server side. | | ALREADYEXISTS | Request ID is already inserted. This status code is returned when all target hosts return `ALREADYEXISTS`. | | NOT_FOUND | Requested ID is NOT inserted. This is the status code of the Update request. | | INTERNAL | Target Vald cluster or network route has some critical error. | `0 (OK)` is also returned when all target hosts return `OK` or `ALREADY_EXISTS`. Mirror Gateway sends an Update request to its host if some requests are `NOT_FOUND`. Therefore, in addition to the , the may also be returned to the user. Here are some common reasons of error. | name | common reason | | :- | :-- | | CANCELLED | Executed cancel() of rpc from client/server-side or network problems between client and server. | | INVALID_ARGUMENT | The Dimension of the request vector is NOT the same as Vald Agent's config, the requested vector's ID is empty, or some request payload is invalid. | | DEADLINE_EXCEEDED | The RPC timeout setting is too short on the client/server side. | | NOTFOUND | Requested ID is NOT inserted. This status code is returned when all target hosts return

| | ALREADYEXISTS | Request a pair of ID and vector is already inserted. This status code is returned when all hosts return `ALREADYEXISTS`. | | INTERNAL | Target Vald cluster or network route has some critical error. | `0 (OK)` is also returned when all target hosts return `OK` or `ALREADY_EXISTS`. The request process may not be completed when the response code is NOT `0 (OK)`. Here are some common reasons of error. | name | common reason | | :- | :-- | | CANCELLED | Executed cancel() of rpc from client/server-side or network problems between client and server. | | INVALID_ARGUMENT | The Dimension of the request vector is NOT the same as Vald Agent's config, the requested vector's ID is empty, or some request payload is invalid. | | DEADLINE_EXCEEDED | The RPC timeout setting is too short on the client/server side. | | ALREADYEXISTS | Requested pair of ID and vector is already inserted. This status code is returned when all target hosts return `ALREADYEXISTS`. | | INTERNAL | Target Vald cluster or network route has some critical error. | `0 (OK)` is also returned when all target hosts return `OK` or `ALREADY_EXISTS`. The request process may not be completed when the response code is NOT `0 (OK)`. Here are some common reasons of error. | name | common reason | | :- | : | | CANCELLED | Executed cancel() of rpc from client/server-side or network problems between client and server. | | INVALID_ARGUMENT | The Requested vector's ID is empty, or some request payload is invalid. | | DEADLINE_EXCEEDED | The RPC timeout setting is too short on the client/server side. | | NOTFOUND | Requested ID is NOT inserted. This status code is returned when all target hosts return `NOTFOUND`. | | INTERNAL | Target Vald cluster or network route has some critical error. | `0 (OK)` is also returned when all target hosts return `OK` or `NOT_FOUND`.