NodeBalancers and the 10k connection limit
I have 2 NodeBalancers in round-robin DNS as I regularly get over 10k connections. I'm creeping up to the per-NodeBalancer limit again now, and it seems a bit silly to have to add another one and configure it. I don't really care about the $10/month, it's just annoying to have to manage this.
Are you planning on improving NodeBalancers so that they can auto-scale, or at least allow the option for me to just change a 2 to a 3 somewhere?
2 Replies
jyoo
Linode Staff
I can definitely see how autoscaling or the ability to clone a NodeBalancer would be helpful. We don't have any plans in the works for this right now, but I've made a note of your feedback so we can look into it for future updates.
I have not tried this, but from looking at the API docs it seems possible.
You could build a small Nodejs app, that checks the status of your NodeBalancers.
Lets say every 30min(depending on your requirements) the Nodejs app checks the API end-point "GET::https://api.linode.com/v4/nodebalancers" and then from that list do a request to "GET::https://api.linode.com/v4/nodebalancers/{nodeBalancerId}/stats".
It seems the response from "GET::https://api.linode.com/v4/nodebalancers/{nodeBalancerId}/stats" gives you the number of connections attached to the nodeBalancer(I assume)…
Depending on your load you can then scale up and down…using "POST::https://api.linode.com/v4/nodebalancers" and "DELETE::https://api.linode.com/v4/nodebalancers/{nodeBalancerId}"
Its not a "out of box" solution but it could help…