Load Balancer Endpoint - "No Workers Available"
I tried using Load Balancer Endpoint today. I got it to work successfully as well. However, after successful uses. I noticed some annoying behavior.
1. When testing, you're going to have lots of test runs, so you'll have to hit the endpoints multiple times. However, once you reached the point of, let's say, the 12th time of sending the task to the worker, it's gonna return "no workers available" despite having it but in "Idle" state.
2. When doing inference (for context, I use LatentSync. So it takes about a good 2-5 mins), I had to manually hit
/ping in order to prevent the worker to become "Idle", which is kind of annoying.
Has anyone experienced this? Any advice would be appreciated!3 Replies
@Almond
Escalated To Zendesk
The thread has been escalated to Zendesk!
I ran into this too. I ended up deleting the endpoint and making a new one. that fixed it. It was working, then at some point no matter what I did it would return no workers available and they would stay idle.
Same here. That’s what I end up doing, then “no workers” again.