Uncatched com.netflix.client.ClientException about teastore HOT 5 CLOSED

Looking at this, it seems like this error would occur if the database is signaling ready, but then the recommender does not receive any data during the training phase.

I've added a retry mechanism here and added the NullpointerException to the exception block (it seems to think that there will never be a ClientException in that block). Could you checkout the version from development and see if this fixed the issue?

from teastore.

Thanks! Is there a Docker image to test your fix?

from teastore.

It seems the github actions for the commit are stuck in queueing, I've retriggered and seems like it is working again so the new images should be available via the :development tag.

Let me know if this already resolves your issue. If it's about temporary connection issues this should resolve it. If the recommends can permanently not reach the persistence despite it being labeled as online, then we will need to take an in depth look at what is going on.

from teastore.

After running a bunch of experiments, I did not see that issue again so I think it's solved.

from teastore.

great to hear, feel free to reopen the issue in case it does pop back up :)

from teastore.