Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The words you're asking for definitions on can be a LOT of different things, and it's generally down to the conventions of the vendor in question as to what they really mean. I can make some typical generalizations though:
1 - a secondary device taking over the role of a primary one if it thinks that device has failed in some critical way
2 - no idea really... could mean a manual failover, not a specifically common phrase to me
3 - typically a number of devices all actively working as a single device. Again though what constitutes a cluster varies wildly.
4 - all of this. High Availability is a very broad umbrella term that covers all many aspects of service resiliency
5 - spreading a load between multiple nodes. Typically this would be a device sitting in front of a number of back end devices to which application requests or such like, are directed based on various algorithms and policies.
Ok, I wasn't sure about switchover. I only heared about it when talking about clustering virtualization solutions...
Anyway, basically a load balanced cluster (HPC) is also a HA cluster. Because when a node fails in a HPC, the load of that node will be devided over the remaining servers. But HPC's are more complex as you need in some cases active/active clustering with master/master replication. Besides that you would use an extra server that will be the director in your HPC. In a production environment you probably would like the director to be clustered for HA as well.
Take good care of your configuration in a HPC, in the future that will come in handy regarding scalability.
Hmm, I'd suggest that if you can go and find these answers on wikipedia yourself, you maybe should ask in the first place??
I would not directly equate failover and HA clusters. the term clustering *usually* suggests 1) arbitrary numbers of devices (maybe hundreds), not pairs as you'd find in a typical failover and also that there is not as often a backup element, but devices are all actively processing data, and failure of a single device would usually just reduce the processing / throughput capacity until it is restored.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.