Shared locking for storage centric exclusive locks

Patent metadata

Field	Value
Publication number	US-9542237-B2
Application number	US-201213602779-A
Country	US
Kind code	B2
Filing date	Sep 4, 2012
Priority date	Sep 4, 2012
Publication date	Jan 10, 2017
Grant date	Jan 10, 2017

Abstract

A computing device receives a request from a host for a shared lock on a resource. The computing device obtains an exclusive lock on the resource using a locking data structure that is stored on the storage domain. The computing device subsequently obtains a shared lock on the resource for the host by writing a flag to the locking data structure, wherein the flag indicates that the host has the shared lock on the resource. The computing device then releases the exclusive lock on the resource.

First claim

What is claimed is:

1. A method comprising:
generating, by a processing device, a first locking data structure and a second locking data structure on a storage device accessed by a host over a network, the first locking data structure providing locks to one or more host identifiers and the second locking data structure providing locks to one or more resources;
acquiring, by the processing device, a lock for the host to one of the host identifiers in response to the host modifying the first locking data structure;
receiving, by the processing device, a request from the host for a shared lock on the resource;
obtaining, by the processing device, an exclusive lock on the resource for the host using the second locking data structure;
subsequently obtaining, by the processing device, the shared lock on the resource for the host by writing a flag to the second locking data structure, wherein the flag indicates the host that has the shared lock on the resource; and
releasing the exclusive lock on the resource after obtaining the shared lock.

2. The method of claim 1 , wherein acquiring the lock to one of the host identifiers comprises using a delta lease procedure, and wherein obtaining the exclusive lock on the resource using the second locking data structure comprises using a Paxos locking procedure.

3. The method of claim 1 , wherein the second locking data structure comprises a bitmap stored in a reserved space on the storage device, the bitmap representing locking states for the resource and for an additional resource, wherein writing the flag to the second locking data structure comprises setting a bit in the bitmap that is associated with the resource and the host.

4. The method of claim 1 , wherein the storage device comprises at least one of a physical storage device or a logical storage device comprising a block domain and the second locking data structure comprises a logical volume on the block domain, and wherein the logical volume comprises a plurality of regions, each of the plurality of regions being associated with a different resource and comprising a plurality of subregions, a first subregion comprising a shared lock bitmap identifying hosts having a shared lock on the resource.

5. The method of claim 1 , wherein the storage device comprises at least one of a physical storage device or a logical storage device comprising a file domain and, wherein the second locking data structure comprises a file in the file domain associated with the resource, the file comprising a plurality of regions, one of the plurality of regions comprising a shared lock bitmap identifying hosts having a shared lock on the resource.

6. The method of claim 1 , wherein the storage device comprises the first locking data structure, the second locking data structure, and the resource, and wherein the host identifier uniquely identifies the host to the storage device.

7. The method of claim 1 , further comprising:
receiving a request from the host for an exclusive lock on a second resource;
granting the exclusive lock on the second resource to the host;
reading the second locking data structure to determine whether any hosts have shared locks on the second resource; and
in response to determining that a second host has a shared lock on the second resource and that an additional criterion is satisfied, revoking the exclusive lock on the second resource from the host and providing a fail result to the host.

8. The method of claim 7 , wherein the additional criterion is that the second host is responsive, the method further comprising:
checking whether the second host is non-responsive; and
in response to determining that the second host is non-responsive, revoking the shared lock from the second host and granting the exclusive lock of the second resource to the host.

9. A non-transitory computer readable storage medium comprising instructions that, when executed by a processing device, cause the processing device to:
generate, by the processing device, a first locking data structure and a second locking data structure on a storage device accessed by a host over a network, the first locking data structure providing locks to one or more host identifiers and the second locking data structure providing locks to one or more resources;
acquire, by the processing device, a lock for the host to one of the host identifiers in response to the host modifying the first locking data structure;
receive, by the processing device, a request from the host for a shared lock on the resource;
obtain, by the processing device, an exclusive lock on the resource for the host using the second locking data structure;
subsequently obtain, by the processing device, the shared lock on the resource for the host by writing a flag to the second locking data structure, wherein the flag indicates the host that has the shared lock on the resource; and
release the exclusive lock on the resource after obtaining the shared lock.

10. The non-transitory computer readable storage medium of claim 9 , wherein acquiring the lock to one of the host identifiers comprise using a delta lease procedure, and wherein obtaining the exclusive lock on the resource using the second locking data structure comprises using a Paxos locking procedure.

11. The non-transitory computer readable storage medium of claim 9 , wherein the second locking data structure comprises a bitmap stored in a reserved space on the storage device, the bitmap representing locking states for the resource and for an additional resource, wherein writing the flag to the second locking data structure comprises setting a bit in the bitmap is associated with the resource and the host.

12. The non-transitory computer readable storage medium of claim 9 , wherein the storage device comprises at least one of a physical storage device or a logical storage device comprising a block domain and the second locking data structure comprises a logical volume on the block domain, and wherein the logical volume comprises a plurality of regions, each of the plurality of regions being associated with a different resource and comprising a plurality of subregions, a first subregion comprising a shared lock bitmap identifying hosts having a shared lock on the resource.

13. The non-transitory computer readable storage medium of claim 9 , wherein the storage device comprises at least one of a physical storage device or a logical storage device comprising a file domain and, wherein the second locking data structure comprises a file in the file domain associated with the resource, the file comprising a plurality of regions, one of the plurality of regions comprising a shared lock bitmap identifying hosts having a shared lock on the resource.

14. The non-transitory computer readable storage medium of claim 9 , wherein the storage device comprises the first locking data structure, the second locking data structure and the resource, and wherein the host identifier uniquely identifies the host to the storage device.

15. The non-transitory computer readable storage medium of claim 9 , wherein the instructions further cause the processing device to:
receive a request from the host for an exclusive lock on a second resource;
momentarily grant the exclusive lock on the second resource to the host;
read the second locking data structure to determine whether any hosts have shared locks on the second resource; and
in response to determining that a second host has a shared lock on the second resource and that an additional criterion is satisfied, revoke the exclusive lock on the second resource from the host and providing a fail result to the

Assignees

• Baron Ayal
• Simoncelli Federico
• Warszawski Eduardo
• Red Hat Israel Ltd

Inventors

• Baron Ayal
• Simoncelli Federico
• Warszawski Eduardo

Classifications

• G06F2209/522

  Manager · CPC title

• G06F9/526 Primary

  Mutual exclusion algorithms · CPC title

• G06F2209/523

  Mode · CPC title