Jump to content

Shared-disk architecture

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Citation bot (talk | contribs) at 16:25, 27 September 2023 (Removed parameters. | Use this bot. Report bugs. | #UCB_CommandLine). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

A shared-disk architecture (SD) is a distributed computing architecture in which the nodes share same disk devices but each node has its own private memory.[1] The disks have active nodes which all share memory in case of any failures.[2] In this architecture the disks are accessible from all the cluster nodes. This architecture has quick adaptability to the changing workloads.[3] It uses robust optimization techniques. It contrasts with shared-nothing architecture, in which all nodes have sole access to distinct disks.[4] Multiple processors can access all disks directly via intercommunication network and every processor has local memory.

Shared Disk has two advantages over Shared Memory. Firstly, each processor has its own memory, the memory bus is not a bottleneck; secondly, the system offers a simple way to provide a degree of fault tolerance.

Shared Disk Architecture

References

  1. ^ "Difference between Shared Nothing Architecture and Shared Disk Architecture". GeeksforGeeks. 2020-05-18. Retrieved 2021-02-24.
  2. ^ "Solar: Towards a Shared-Everything Database on Distributed Log-Structured Storage" (PDF): 13 – via Solar. {{cite journal}}: Cite journal requires |journal= (help)
  3. ^ Rylan, John (1 April 2018). "Big Database (Part 2): Database Architecture". DZone.
  4. ^ "Shared Nothing v.s. Shared Disk Architectures: An Independent View". November 24, 2009. Retrieved November 1, 2012.