Concurrent access to RAID data in shared storage

• US 20060129559A1
• Filed: 12/15/2004
• Published: 06/15/2006
• Est. Priority Date: 12/15/2004
• Status: Abandoned Application

• Current Assignee: Dell Products LP (Dell Technologies Inc.)
• Original Assignee: Dell Products LP (Dell Technologies Inc.)
• Inventors: Najafirad, Peyman, Sankaran, Ananda C.
• Application Number:
  US11/012,586
• Publication Number:
  US 20060129559A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component
• CPC Class Codes: G06F 11/2048 where the redundant components share neither address space nor persistent storage
• CPC Class Codes: G06F 11/2082 Data synchronisation
• CPC Class Codes: G06F 16/2336 Pessimistic concurrency control approaches, e.g. locking or multiple versions without time stamps
• CPC Class Codes: G06F 2201/80 Database-specific techniques

Abstract

A system and method is disclosed for managing the serving of read and write commands in a computer cluster system having redundant storage. A plurality of database servers is included in the computer cluster network to serve read and write commands from the database clients of the network. One of the database servers is configured to handle both read commands and write commands. The remainder of the database servers are configured to handle only read commands. The database of the computer system includes a redundant storage subsystem that involves the use of mirrored disks associated with each of the database servers.

Claims

1. A computer network, comprising:

a plurality of database servers, wherein one database server of the set of database servers is designated as being operable to serve write command and wherein each database server of the set of database servers is operable to serve read commands;

a shared redundant storage network coupled to the database servers, wherein the redundant storage network includes a plurality of mirrored sets of the storage data of the storage network, and wherein each set of storage data is associated with one of the database servers;

wherein the set of storage data associated with the database server that is designated to serve write command is operable to propagate to the other sets of storage data the data of any write commands served by the database server designated to serve write commands.

2. The computer network of claim 1, wherein the shared redundant storage network comprises RAID storage.

3. The computer network of claim 1, wherein the shared redundant storage network comprises RAID 1/0 storage.

4. A computer network, comprising:

a plurality of clients;

a first server coupled to the plurality of clients;

a second server coupled to the plurality of clients, wherein only the first server designated as being operable to server write commands from any of the clients and wherein each of the first server and the second server is designated as being operable to serve read commands from any one of the clients; and

a storage network coupled to the plurality of servers, wherein the storage network includes a first logical unit coupled to the first server and a second logical unit coupled to the second server, and wherein the data of write commands stored in the first logical unit are propagated to the second logical unit.

5. The computer network of claim 4, wherein the storage elements of the first logical unit and the storage elements of the second logical unit are collectively organized to store data according to a RAID storage methodology.

6. The computer network of claim 4, wherein the storage elements of the first logical unit and the storage elements of the second logical unit are collectively organized to store data according to a RAID 1/0 storage methodology in which the data content of a first drive of the first logical unit is a duplicate of the data content of the first drive of the second logical unit, and the data content of a second drive of the first logical unit is a duplicate of the data content of the second drive of the second logical unit.

7. The computer network of claim 4, wherein the storage elements of the first logical unit and the storage elements of the second logical unit are collectively organized to store data according to a RAID 1 storage methodology in which each drive of the first logical unit is mirrored in a corresponding drive of the second logical unit.

8. The computer network of claim 4, further comprising an arbiter associated with the clients of the computer network for distributing writes to the first server of the computer network and for distributing read command to the first server or the second server of the computer system on the basis of the relative load conditions of the servers.

9. A method for managing read and write commands in a computer network having a set of database servers coupled to common storage, comprising:

providing a first database server within the set of database servers, wherein the first database server is operable to handle read commands and is the only database server among the set of database servers that is operable to serve write commands;

providing one or more read-only database servers within the set of database servers, wherein each of the read-only database server is not operable to handle write commands and is operable to handle read commands;

providing a plurality of logical units, wherein each one of the logical units is uniquely associated with one of the database servers of the set of database servers;

distributing a write command to the first database server;

saving the data of the write command to the logical unit that is associated with the first database server;

propagating the data of the write command from the logical unit associated with the first database server to each other logical units.

10. The method for managing read and write commands in a computer network of claim 9, wherein the plurality of logical units comprise a redundant storage methodology that is operable to save data according to a RAID storage methodology.

11. The method for managing read and write commands in a computer network of claim 9, wherein the plurality of logical units comprise a redundant storage methodology that is operable to save data according to a RAID methodology in which the content of each logical unit is a duplicate of each other logical unit in the plurality of logical units.

12. The method for managing read and write commands in a computer network of claim 9,

wherein the first database server is coupled to a first logical unit within the plurality of logical units;

wherein each of the other database servers is coupled to a unique logical unit within the plurality of logical units; and

wherein the content of the first logical unit is mirrored across the logical units coupled to each of the other database servers of the computer network.

13. The method for managing read and write commands in a computer network of claim 9,

wherein the first database server is coupled to a first logical unit within the plurality of logical units, and wherein the first logical unit includes a plurality of drives;

wherein each of the other database servers is coupled to a unique logical unit within the plurality of logical units, and wherein each unique logical unit includes a plurality of drives that are respectively identical to each of the drives of the first logical unit.

14. The method for managing read and write commands in a computer network of claim 9, further comprising the steps of:

disabling the ability to read from logical units not associated with the first database server following the initiation of a write to the logical unit associated with the first database server; and

enabling the ability to read from the logical units not associated with the first database server following the propagation of the data of the write command to each of the logical units not associated with the first database server.

15. The method for managing read and write commands in a computer network of claim 12, further comprising the steps of:

identifying the failure of a drive of a logical unit;

identifying a logical unit that includes a complete set of drives;

designating a logical unit that includes a complete set of drive as the logical unit associated with the first database server; and

disabling the ability of the database servers other than the first database server to serve read commands.

16. The method for managing read and write commands in a computer network of claim 15, further comprising the steps of:

rebuilding the failed drive of the logical unit; and

enabling the ability of the database servers other than the first database server to serve read commands.

17. A computer network, comprising:

a plurality of database clients;

a plurality of database servers, wherein each database client is operable to transmit commands to each of the database servers, wherein the plurality of database servers includes one write database server, and wherein only the write database server is operable serve write commands to the database clients; and

a database coupled to the database servers, wherein the database includes a plurality of mirrored storage elements, wherein each storage element is uniquely associated with one of the database servers, and wherein a write stored in the storage element associated with the write database server is propagated to each of the other storage elements of the database.

18. The computer network of claim 17, further comprising an arbiter associated with the database clients, wherein the arbiter is operable to transmit all write commands from the database clients to the write database server and is operable to transmit all read commands to one of the plurality of database servers on the basis of the load of the database servers.

19. The computer network of claim 17, wherein the mirrored storage elements store data according to a RAID storage methodology.

20. The computer network of claim 17, wherein the mirrored storage elements store data according to a RAID 1/0 storage methodology in which the drives of the storage element associated with the write database server are mirrored in each of the drives of the other storage elements of the database.