You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey,
At the moment, this gem only uses the first server from the array we pass, I think it would be very useful to use all of them because sometime under heavy load or when running a lot of request in a short duration, queries ended up failing.
I think it's not because the cluster cannot process the request but simply because of HTTP requests saturation.
I'm willing to work on a patch for this but I'd like your approval first ; mostly to know if it's recommended to run queries directly on secondary nodes while queries are running on the primary. I'm pretty sure it works, but I'm not sure it's recommended.
What I have in mind right now (didn't start coding anything):
Retry on a different server if request fails
Simple load balancing (round roaming)
(Maybe) Advanced load balancing depending on the individual load of each node of the cluster (if possible)
indeed, the client should use multiple hosts for failover scenarios. the best way to implement that is round robin "load balancing". you can perform any query on any node of the cluster. using multiple hosts for queries helps to reduce load on each of the handler nodes.
Hey,
At the moment, this gem only uses the first server from the array we pass, I think it would be very useful to use all of them because sometime under heavy load or when running a lot of request in a short duration, queries ended up failing.
I think it's not because the cluster cannot process the request but simply because of HTTP requests saturation.
I'm willing to work on a patch for this but I'd like your approval first ; mostly to know if it's recommended to run queries directly on secondary nodes while queries are running on the primary. I'm pretty sure it works, but I'm not sure it's recommended.
What I have in mind right now (didn't start coding anything):
Let me know what you think,
Cheers,
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: