Open rawaa123 opened 5 days ago
You should probably introduce reasonable timeouts for background jobs.
Thank you for the suggestion. I am working on this and will need some time to finish. In the meantime, is it possible to restart it for now as an urgent and quick fix, because till now the recommendation is not working since its stuck for many days and is not being usable for other ones.
In edge:
In live:
I temporarily scaled them up to 2 (edge) and 4 (prod) workers.
@ralf-berger Thank you. After this change, the recommendation is working smoothly. However, why is this a temporary solution and we cant keep it permanently? The reason is that since the start we wanted to have at least more than one worker but we couldn't because of the lack of resources. Now, if we have the resources available, can we keep this change permanently?
I noticed that the webserver (sc-coursemapper-webserver-coursemapper-kg-recommendation) is stuck for a while since now in both live and edge, could you please restart it? We previously attempted to generate recommendations, and it was working, but now it seems to be stuck. Any suggestions?