Computer cluster: Difference between revisions

Revision as of 19:28, 20 July 2024

Latest revision as of 00:28, 3 May 2025

(6 intermediate revisions by 5 users not shown)

Line 1:

{{Short description|Set of computers configured in a distributed computing system}}

{{Distinguish|data cluster|grid computing}}

{{Redirect|Cluster computing|the journal|Cluster Computing (journal)}}

Line 6 ⟶ 7:

[[File:Taiwania series.jpg|thumb|[[Taiwania_(supercomputer)|Taiwania]] series uses cluster architecture.]]

A '''computer cluster''' is a set of [[computerscomputer]]s that work together so that they can be viewed as a single system. Unlike [[Grid computing|grid computer]]s, computer clusters have each [[Node (networking)|node]] set to perform the same task, controlled and scheduled by software. The newest manifestation of cluster computing is [[cloud computing]].

The components of a cluster are usually connected to each other through fast [[local area network]]s, with each [[Node (networking)|node]] (computer used as a server) running its own instance of an [[operating system]]. In most circumstances, all of the nodes use the same hardware<ref>{{cite web |url=https://stackoverflow.com/questions/9723040/what-is-the-difference-between-cloud-grid-and-cluster |title=Cluster vs grid computing |website=[[Stack Overflow]]}}</ref>{{better source needed|date=June 2017}} and the same operating system, although in some setups (e.g. using [[Open Source Cluster Application Resources]] (OSCAR)), different operating systems can be used on each computer, or different hardware.<ref name=pcauthority>{{cite web|url=http://www.pcauthority.com.au/Feature/306972,weekend-project-build-your-own-supercomputer.aspx|title=Weekend Project: Build your own supercomputer|date=29 June 2012|first=Darien|last=Graham-Smith|website=PC & Tech Authority|access-date=2 June 2017}}</ref>

Clusters are usually deployed to improve performance and availability over that of a single computer, while typically being much more cost-effective than single computers of comparable speed or availability.<ref>{{cite web|url=http://www.cc.gatech.edu/~bader/papers/ijhpca.html|title=Cluster Computing: Applications|last1=Bader|first1=David|author-link=David Bader (computer scientist)|date=May 2001|publisher=[[Georgia Institute of Technology College of Computing|Georgia Tech College of Computing]]|first2=Robert|last2=Pennington|access-date=2017-02-28|archive-url=https://web.archive.org/web/20071221011621/http://www.cc.gatech.edu/~bader/papers/ijhpca.html|archive-date=2007-12-21|url-status=dead}}</ref>

Line 51 ⟶ 52:

"[[High-availability cluster]]s" (also known as [[failover]] clusters, or HA clusters) improve the availability of the cluster approach. They operate by having redundant [[Node (networking)|nodes]], which are then used to provide service when system components fail. HA cluster implementations attempt to use redundancy of cluster components to eliminate [[single point of failure|single points of failure]]. There are commercial implementations of High-Availability clusters for many operating systems. The [[Linux-HA]] project is one commonly used [[free software]] HA package for the [[Linux]] operating system.

==Benefits==

<!-- This used to be a list. Work has been done since, but it's still incomplete. -->

Clusters are primarily designed with performance in mind, but installations are based on many other factors. Fault tolerance (''the ability forof a system to continue workingoperating withdespite a malfunctioning node'') allows forenables [[horizontal scaling|scalability]], and in high-performance situations, allows for a low frequency of maintenance routines, resource consolidation (e.g., [[RAID]]), and centralized management. Advantages include enabling data recovery in the event of a disaster and providing parallel data processing and high processing capacity.<ref>{{cite web|url=http://www-03.ibm.com/systems/clusters/benefits.html|title=IBM Cluster System : Benefits|publisher=[[IBM]]|access-date=8 September 2014|archive-url=https://web.archive.org/web/20160429022854/http://www-03.ibm.com/systems/clusters/benefits.html|archive-date=29 April 2016|url-status=dead}}</ref><ref>{{cite web|url=https://technet.microsoft.com/en-us/library/cc778629(v=ws.10).aspx|title=Evaluating the Benefits of Clustering|date=28 March 2003|publisher=[[Microsoft]]|access-date=8 September 2014|archive-url=https://web.archive.org/web/20160422092651/https://technet.microsoft.com/en-us/library/cc778629%28v%3Dws.10%29.aspx|archive-date=22 April 2016|url-status=dead}}</ref>

In terms of scalability, clusters provide this in their ability to add nodes horizontally. This means that more computers may be added to the cluster, to improve its performance, redundancy and fault tolerance. This can be an inexpensive solution for a higher performing cluster compared to scaling up a single node in the cluster. This property of computer clusters can allow for larger computational loads to be executed by a larger number of lower performing computers.

Line 157 ⟶ 159:

:* [[Solaris Cluster]]

:* [[Veritas Cluster Server]]

:* [[Beowulf cluster]]

''Computer farms''

Line 177 ⟶ 180:

{{Commons category|Clusters (computing)}}

* [https://web.archive.org/web/20190219183441/https://www.ieeetcsc.org/ IEEE Technical Committee on Scalable Computing (TCSC)]

* [https://archive.today/20130103192843/http://publib.boulder.ibm.com/infocenter/clresctr/vxrx/index.jsp?topic=%2Fcom/com.ibm.cluster.rsct.doc%2Frsctbooks/rsctbooks.html Reliable Scalable Cluster Technology, IBM]{{Dead link|date=July 2020 |bot=InternetArchiveBot |fix-attempted=yes }}

* [https://www.ibm.com/developerworks/wikis/display/tivoli/Tivoli+System+Automation Tivoli System Automation Wiki]

* [https://static.googleusercontent.com/media/research.google.com/en/us/pubs/archive/43438.pdf Large-scale cluster management at Google with Borg], April 2015, by Abhishek Verma, Luis Pedrosa, Madhukar Korupolu, David Oppenheimer, Eric Tune and John Wilkes