Data processing lock signal transmission

Patent metadata

Field	Value
Publication number	US-9887908-B2
Application number	US-201514885938-A
Country	US
Kind code	B2
Filing date	Oct 16, 2015
Priority date	Feb 22, 2013
Publication date	Feb 6, 2018
Grant date	Feb 6, 2018

Abstract

In accordance with one aspect of the present description, a node of the distributed computing system has multiple communication paths to a data processing resource lock which controls access to shared resources, for example. In this manner, at least one redundant communication path is provided between a node and a data processing resource lock to facilitate reliable transmission of data processing resource lock signals between the node and the data processing resource lock. Other features and aspects may be realized, depending upon the particular application.

First claim

What is claimed is:

1. A computer program product for a distributed computing system having a plurality of processor nodes including a first processor node, the computer program product comprising a computer readable storage medium having computer readable program code embodied therein for execution by a processor of the first processor node to perform operations, the operations comprising:
under control of a first processor node of a distributed computer storage system,
transmitting over a first communication path to a shared hardware resource lock device, a first request to be granted a shared hardware resource lock of the hardware resource lock device;
determining whether a communication failure has occurred over the first communication path in connection with the transmission of the first request; and
upon determining that a communication failure has occurred over the first communication path in connection with the transmission of the first request, transmitting over a second communication path to the shared hardware resource lock device, a second request to be granted the shared hardware resource lock of the shared hardware resource lock device.

2. The computer program product of claim 1 wherein the operations further comprise receiving by said first processor node a grant of a request to be granted the shared hardware resource lock of the shared hardware resource lock device, and, performing by the first processor node a failover which includes accessing shared hardware resources using the shared hardware resource lock held by the first processor node.

3. The computer program product of claim 1 wherein the operations further comprise receiving by said first processor node a grant of a request to be granted the shared hardware resource lock of the shared hardware resource lock device, and, performing by the first processor node a procedure which includes accessing shared hardware resources using the shared hardware resource lock held by the first processor node.

4. The computer program product of claim 1 wherein the shared hardware resource lock device is a failover lock device controlling access to shared resources for a failover procedure, the operations further comprise upon determining that a communication failure has not occurred over the first communication path in connection with the transmission of the first request, and in response to not receiving by said first processor node a grant of a request to be granted the shared hardware resource lock of the shared hardware resource lock device, rebooting the first processor node.

5. The computer program product of claim 1 wherein the shared hardware resource lock device is a failover lock device controlling access to shared resources for a failover procedure, the operations further comprise upon determining that a communication failure has occurred over the second communication path in connection with the transmission of the second request, rebooting the first processor node.

6. The computer program product of claim 1 wherein the shared hardware resource lock device is a failover lock device controlling access to shared resources for a failover procedure, the operations further comprise upon determining that a communication failure has not occurred over the second communication path in connection with the transmission of the second request, and in response to not receiving by said first processor node a grant of a request to be granted the shared hardware resource lock of the shared hardware resource lock device, rebooting the first processor node.

7. A distributed computing storage controller system for use with a plurality of hosts and a plurality of storage devices, comprising:
a plurality of processor nodes including a first processor node having a processor, said processor nodes for transferring data between the plurality of hosts and the plurality of storage devices;
a memory having a plurality of units of shared data;
a plurality of shared resources;
a data processing lock device providing a data processing lock for controlling access by said plurality of nodes to at least one of said units of shared data and said shared resources;
first and second communication paths coupling said first processor node to said data processing lock device; and
a computer program product comprising a computer readable storage medium having computer readable program code embodied therein for execution by a processor of the first processor node to perform operations, the operations comprising:
under control of a first processor node of a distributed computer storage system,
transmitting over a first communication path to a shared hardware resource lock device, a first request to be granted a shared hardware resource lock of the hardware resource lock device;
determining whether a communication failure has occurred over the first communication path in connection with the transmission of the first request; and
upon determining that a communication failure has occurred over the first communication path in connection with the transmission of the first request, transmitting over a second communication path to the shared hardware resource lock device, a second request to be granted the shared hardware resource lock of the shared hardware resource lock device.

8. The distributed computing storage controller system of claim 7 wherein the operations further comprise receiving by said first processor node a grant of a request to be granted the shared hardware resource lock of the shared hardware resource lock device, and, performing by the first processor node a failover which includes accessing shared hardware resources using the shared hardware resource lock held by the first processor node.

9. The distributed computing storage controller system of claim 7 wherein the operations further comprise receiving by said first processor node a grant of a request to be granted the shared hardware resource lock of the shared hardware resource lock device, and, performing by the first processor node a procedure which includes accessing shared hardware resources using the shared hardware resource lock held by the first processor node.

10. The distributed computing storage controller system of claim 7 wherein the shared hardware resource lock device is a failover lock device controlling access to shared resources for a failover procedure, the operations further comprise upon determining that a communication failure has not occurred over the first communication path in connection with the transmission of the first request, and in response to not receiving by said first processor node a grant of a request to be granted the shared hardware resource lock of the shared hardware resource lock device, rebooting the first processor node.

11. The distributed computing storage controller system of claim 7 wherein the shared hardware resource lock device is a failover lock device controlling access to shared resources for a failover procedure, the operations further comprise upon determining that a communication failure has occurred over the second communication path in connection with the transmission of the second request, rebooting the first processor node.

12. The distributed computing storage controller system of claim 7 wherein the shared hardware resource lock device is a failover lock device controlling access to shared resources for a failover procedure, the operations further comprise upon determining that a communication failure has not occurred over the second communication path in connection with the transmission of the second request, and in response to not receiving by said first processor node a grant of a request to be granted the shared

Assignees

• IBM

Inventors

• Colpo Yolanda
• Elliott John C
• Garcia Enrique Q
• Juarez Larry
• Sorenson Todd C

Classifications

• G06F2201/805

  Real-time · CPC title

• G06F21/70

  Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer · CPC title

• G06F11/0757

  by exceeding a time limit, i.e. time-out, e.g. watchdogs · CPC title

• G06F11/221

  to test buses, lines or interfaces, e.g. stuck-at or open line faults · CPC title

• G06F11/2033

  switching over of hardware resources · CPC title