New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
how to setup a HA network with multiple LES?
I'm trying to understand how to setup a HA with different les in different locations but I can't seem to understand how something more than a round robin setup could work as 100% uptime and load balancers. I read the thread on les forums but it's not clear to me. Does anyone use something similar?
Comments
Just have more that one thing every step of the way with a mechanism that makes sure the next step is always online, so multiple DNS servers that change the record to point to a server that is online, multiple haproxy servers to point DNS to and multiple servers behind haproxy (LES) that run your application with multiple database servers.
Proper HA isn't easy, stuff like domain provider DNS and billing issues will always be out of your control.
Well, using Rage4 with DNS Failover and Statuscake/UptimeRobot is a start.
But 5 Minute checks are pain the ass.
Other than a fun proof of concept project, why would you host anything HA on LES?
@mpkossen did a "Low End Cluster" series on LEB: https://lowendbox.com/blog/tutorial-the-lowendcluster-part-1/ (4 parts total)
I think that will be hard with LES and you'd likely need something like keepalived to do proper failover and I doubt that will work with LES given you don't control the IPs [and they're not dedicated].
It can be done in some use cases but you need to be specific about what exactly you want 100% uptime for, static site, Wordpress, mine craft, team speak etc etc.
LES forum is probably the right place to discus it.
a php website
Please don't take offence, but do you think you could possibly give me/us less information? haha
If you mean a static php site with no frills then that is simple enough.
I'm sorry it's of course a dynamic website using a database
MySQL: master<>master<>master
Rsync the static files on a 5 minute update window
Use a DNS service with auto fail/remove when a site is down, I believe GBhouse's stuff does that, or get a anycast IP from them.
Setup your site records in haproxy/nginx reverse proxy.
Use at least 3 locations.
That's the ridiculously simple version for here, but unless you can give a lot more detail you are essentially saying, "I have an engine and a car, how do I make it go?"
These tutorials are, understandably, DO-centric, but they can be implemented equally well on VM's with other providers offering floating IP's, like LunaNode, for one. Enjoy!
https://www.digitalocean.com/community/tutorials/what-is-high-availability
https://www.digitalocean.com/community/tutorials/how-to-set-up-highly-available-haproxy-servers-with-keepalived-and-floating-ips-on-ubuntu-14-04
https://www.digitalocean.com/community/tutorials/how-to-create-a-high-availability-setup-with-heartbeat-and-floating-ips-on-ubuntu-14-04
https://www.digitalocean.com/community/tutorials/how-to-set-up-highly-available-web-servers-with-keepalived-and-floating-ips-on-ubuntu-14-04
Here is a good read from the LES forum
http://forum.lowendspirit.com/viewtopic.php?id=745
Start there and look for possible failure points, improve on those and you are good to go.