In distributed computing, a Single system image cluster is a cluster of machines that appears to be one single system. [1] [2] The interest in SSI clusters is based on the perception that they may be simpler to use and administer that more specialized clusters. Different SSI systems may provide a more or less complete illusion of a single system.
Features of SSI clustering systems edit
Different SSI systems may, depending one their intended usage, provide some subset of these features.
Process migration edit
Many SSI systems provide process migration.[3] Processes may start on one node and be moved to another node, possibly for resource balancing or administrative reasons[note 1]. As processes are moved from one node to another other associated resources, for example IPC resources may be moved with them.
Process checkpointing edit
Some SSI systems allow checkpointing of running processes, allowing their current state to be saved and reloaded at a later date.[note 2] Checkpointing can be seen as related to migration, migrating a process from one node to another can be implemented by first checkpointing the process, then restarting it on another node. Alternatively checkpointing can be considered as migration to disk.
Single process space edit
Some SSI systems provide the illusion that all processes are running on the same machine - the process management tools (e.g. "ps", "kill" on Unix like systems) operate on all processes in the cluster.
Single root edit
Most SSI systems provide a single view of the file system. This may be achieved by a simple NFS server, shared disk devices or even file replication.
The advantage of a single root view is that processes may be run on any available node and access needed files with no special precautions. If the cluster implements process migration a single root view enables direct accesses to the files from the node where the process is currently running.
Some SSI systems provide a way of "breaking the illusion", having some node-specific files even in a single root, e.g. HP TruCluster provides a "context dependent symbolic link" (CDSL) which points to different files depending on the node that accesses it. This may be necessary to deal with heterogeneous clusters, where not all nodes have the same configuration.
Single I/O space edit
Some SSI systems allow all nodes access the I/O devices (e.g. tapes, disks, serial lines and so on) of other nodes. There may be some restrictions on the kinds of accesses allowed (For example OpenSSI can't mount disk devices from one node on another node).
Single IPC space edit
Some SSI systems allow processes on different nodes to communicate using inter-process communications mechanisms as if they were running on the same machine. On some SSI systems this can even include shared memory.
In most cases inter-node IPC will be slower than IPC on the same machine, possibly drastically slower for shared memory. Some SSI clusters include special hardware to reduce this slowdown.
Cluster IP address edit
Some SSI systems provide a "cluster address", a single address visible from outside the cluster that can be used to contact the cluster as if it were one machine. This can be used for load balancing inbound calls to the cluster, directing them to lightly loaded nodes, or for redundancy, moving the cluster address from one machine to another as nodes join or leave the cluster.[note 3]
Some example SSI clustering systems edit
| Name | Process migration | Process checkpoint | Single process space | Single root | Single I/O space | Single IPC space | Cluster IP address[t 1] |
|---|---|---|---|---|---|---|---|
| Amoeba[t 2] | |||||||
| AIX TCF[t 3] | y | ||||||
| BProc[t 4] | y | ||||||
| DragonFly BSD[t 5] | |||||||
| Genesis | |||||||
| Inferno | |||||||
| Kerrighed | y | y | y | y | y | ||
| LinuxPMI[t 6] | y | y | n | y | n | n | |
| LOCUS[t 7] | y | y | y | y[t 8] | |||
| MOSIX | y | y | n | y | n | n | |
| Nomad[t 9] | y | y | y | ||||
| openMosix[t 10] | y | y | n | y | n | n | |
| Open-Sharedroot[t 11] | n | n | n | y | n | n | |
| OpenSSI | y | n | y | y | y | y | y |
| OpenVMS | |||||||
| Plan 9 | |||||||
| Plurix | |||||||
| Sprite[t 12] | y | n | y | y | n | ||
| TruCluster[t 13] | n | n | y | n | n | n |
- ^ Many of the Linux based SSI clusters can use the Linux Virtual Server to implement a single cluster IP address
- ^ Amoeba appears to be inactive
- ^ AIX TCF was available in AIX 1. It is currently inactive
- ^ Bproc is the Beowulf Distributed Process Space
- ^ A "long term goal" of DragonFly is to achieve SSI
- ^ LinuxPMI is a successor to openMosix
- ^ LOCUS is currently inactive
- ^ LOCUS used named pipes for IPC
- ^ Eduardo Pinheiro; Ricardo Bianchini, The Nomad Project
{{citation}}: CS1 maint: multiple names: authors list (link) - ^ openMosix was a fork of MOSIX, now inactive
- ^ Open-Sharedroot is a shared root Cluster from ATIX
- ^ Sprite is inactive.
- ^ TruCluster is part of the Tru64 operating system from Hewlett-Packard
See also edit
Notes edit
- ^ for example it may be necessary to move long running processes off a node that is to be closed down for maintenance
- ^ Checkpointing is particularly useful in clusters used for high-performance computing, avoiding lost work in case of a cluster or node restart
- ^ "leaving a cluster" is often a euphemism for crashing
References edit
- ^ Pfister, Gregory F. (1998), In search of clusters, Upper Saddle River, NJ: Prentice Hall PTR, ISBN 978-0138997090, OCLC 38300954
- ^ Buyya, Rajkumar; Cortes, Toni; Jin, Hai (2001), "Single System Image" (PDF), International Journal of High Performance Computing Applications, 15 (2): 124, doi:10.1177/109434200101500205
{{citation}}: CS1 maint: multiple names: authors list (link) - ^ Smith, Jonathan M. (1988), "A survey of process migration mechanisms" (PDF), ACM SIGOPS Operating Systems Review, 22: 28, doi:10.1145/47671.47673
[[Category:Distributed computing]]
es:Single System Image it:Single-system image nl:Single-system image pl:Single System Image zh:单系统映象