Aditya
Aditya
@LalitDeore quickly finish this soon? :)
Looking into it.
Since most of our users use Opensearch with our docker-compose, we haven't had to deal with cloud provider rate limits yet. We can investigate however and optimise this on a...
timeouts might be a red herring. @salamander04 can you show me your backend logs? do you find any nil pointers?
> shuffle-orborus | 2025/11/06 09:24:01 [ERROR][d78234e4-d6c3-4f5e-8ab4-fb34039a3c93] Error running worker request to http://shuffle-workers:33333/api/v1/execute (1): Post "http://shuffle-workers:33333/api/v1/execute": dial tcp: lookup shuffle-workers on 127.0.0.11:53: server misbehaving this looks like a different issue caused...
We have identified a cause for this issue. We are working on a fix, thank you for reporting it. It has something to do with docker depreciating how they handle...
Can you run `docker version` in your system? @salamander04 Trying to see something.
Checks out with what we observed. @ben-5555 @salamander04 if your workers are timing out, can you grep out "nil" in the backend logs? I am trying to see something.
Actually, I read your original issue again. Seems like backend isn't able to reach to opensearch. Can you check if your opensearch instance is healthy?
Leaving this info here, so that it's helpful for anyone who found this issue while searching for it: > shuffle-orborus | 2025/11/06 09:24:01 [ERROR][d78234e4-d6c3-4f5e-8ab4-fb34039a3c93] Error running worker request to http://shuffle-workers:33333/api/v1/execute...