Shared-disk architecture: Difference between revisions

Content deleted Content added
added in use template
WikiCleanerBot (talk | contribs)
m v2.05b - Bot T20 CW#61 - Fix errors for CW project (Reference before punctuation)
 
(8 intermediate revisions by 6 users not shown)
Line 1:
{{refimprove|date=November 2012}}{{In use}}
A '''shared-disk architecture''' (SD) is a [[distributed computing]] [[Software architecture|architecture]] in which the nodes share same disk devices but each node has its own private memory.<ref>{{Cite web|date=2020-05-18|title=Difference between Shared Nothing Architecture and Shared Disk Architecture|url=https://www.geeksforgeeks.org/difference-between-shared-nothing-architecture-and-shared-disk-architecture/|access-date=2021-02-24|website=GeeksforGeeks|language=en-US}}</ref> The disks have active nodes which all share memory in case of any failures.<ref>{{Cite journal|title=Solar: Towards a Shared-Everything Database on Distributed Log-Structured Storage|url=https://www.cs.utah.edu/~dongx/paper/solar-atc.pdf|journal=|pages=13|via=Solar}}</ref> In this architecture, the disks are accessible from all the cluster nodes. This architecture has quick adaptability to the changing workloads.<ref>{{Cite web|last=Rylan|first=John|date=1 April 2018|title=Big Database (Part 2): Database Architecture|url=https://dzone.com/articles/big-database-2-database-architecture|website=DZone}}</ref> It uses robust optimization techniques. Multiple processors can access all disks directly via intercommunication network and every processor has local memory.
 
AIt '''sharedcontrasts disk architecture''' (SD) is awith [[distributedshared-nothing computingarchitecture]] architecture, in which all disksnodes arehave accessiblesole fromaccess allto clusterdistinct nodes.disks,<ref name="stopford">{{cite web |date=November url=http://www.benstopford.com/2009/11/24/understanding-the-shared-nothing-architecture/, |2009 |title=Shared Nothing v.s. Shared Disk Architectures: An Independent View | dateurl=November http://www.benstopford.com/2009/11/24, 2009/understanding-the-shared-nothing-architecture/ | accessdateaccess-date=November 1, 2012}}</ref> It contrastsand with [[shared nothingShared-memory architecture|shared-memory]], in which all nodes have sole access to distinct disks.<ref name=stopford/> Multiple processors can access all disks directly via intercommunication network and every processorthey hasalso localshare memory.
 
Shared Disk-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.
 
[[File:Shared Disk Architecture.jpg|thumb|Shared Disk Architecture]]