Client Side Troubleshooting

This page introduces the popular troubleshooting for client side.

The flow chart helps you find the root reason for your problem.

Additionally, if you encounter some errors when using API, the API status code helps you, too.

Insert Operation

Please check your container limit of memory at first. Vald Agent requires memory for keeping indexing on memory.

kubectl describe statefulset vald-agent-ngt

If the limit of memory exists, please remove it or update the value to more enormous.

There are two possible reasons.

Indexing has not finished in Vald Agent
Vald will search the nearest vectors of query from the indexing in Vald Agent. If the indexing process is running, Vald Agent returns no search result.
It will resolve when completed indexing instructions, like CreateIndex.
Too short timeout for searching
When the search timeout configuration is too short, Vald LB Gateway stops the searching process before getting the search result from Vald Agent.
In the sense of search operation, you can modify search timeout by payload config.

It is easy to find out which problem occurs by inspections of the log of each Pod, like stern.

Vald Agent NGT requires an AVX2 processor for running. Please check your CPU information.