Discipline for lock reassertion in a distributed file system
View Patent ↗A method and system for asserting a lock in a distributed file system is provided. All distributed locks have a lease for a limited time period, wherein the lease may be renewed periodically. A lock manager data structure is provided to maintain mode compatibility of locks granted to different client nodes for the same object. The process of acquiring or reasserting a lock includes determining whether there are other valid locks in use, as well as whether a valid lock is in operation in a conflicting or compatible mode with a requested lock. A new lock lease may be granted and a lock lease which has expired may be reasserted if a conflicting lease is not present.
1. A computer implemented method for reasserting a lock in a distributed file system comprising:
creating a lock manager data structure in volatile memory for an object assigned a distributed lock; and
assigning an identifying number to a file system in which said object is located, said file system identifying number adapted to be incremented upon a restart of a server assigned to said file system;
comparing a file system identifying number provided by a client requesting a lock on said system object with a current file system identifying number in which said object is located; and
granting a lock reassertion request to said requesting client subsequent to breaking a lock if said compared file system identifying numbers are within an appropriate range.
2. The method of claim 1 , further comprising restoring cache consistency between a client node and a server node upon reasserting a lock request subsequent to loss of a lock lease.
3. The method of claim 2 , wherein the step of restoring cache consistency between a client node and said server node includes merging client node data attributes with server node data attributes.
4. The method of claim 1 , further comprising deferring commitment of a new filesystem identifying number in persistent storage until expiration of a lock reassertion grace period.
5. The method of claim 1 , further comprising notifying a client of theft of a lock on which said client possesses a compatible lock.
6. The method of claim 1 , wherein said data structure includes data selected from the group consisting of: a list of locks held by each client node, a lock mode for each lock, a state of any pending demands, and a set of lock modes granted on an object.
7. A data storage system comprising:
a lock manager data structure for a system object assigned a distributed lock from a server, wherein said data structure is in volatile memory;
an identifying number assigned to a file system in which said object is located, said file system identifying number adapted to be incremented upon a restart of said server assigned to said file system; and
a manager adapted to compare a file system identifying number provided by a client requesting a lock on said system object with a current file system identifying number in which said object is located, and to grant a lock reassertion request to said requesting client subsequent to breaking a lock if said compared file system identifying numbers are within an appropriate range.
8. The system of claim 7 , further comprising a cache manager adapted to restore cache consistency between said client node and said server in conjunction with a reassert of a lock request from said client subsequent to loss of a lock lease.
9. The system of claim 8 , wherein said cache manager merges client attributes with server data attributes.
10. The system of claim 7 , further comprising a filesystem manager adapted to defer commitment of a new filesystem identifying number in persistent storage until expiration of a lock reassertion grace period.
11. The system of claim 7 , further comprising a lock theft manager adapted to notify said client node of theft of a lock on which said client possesses a compatible lock.
12. The system of claim 7 , wherein said data structure includes data selected from the group consisting of: a list of locks held by each client node, a lock mode for each lock, a state of any pending demands, and a set of lock modes granted on an object.
13. An article comprising:
a computer-readable signal-bearing medium;
means in the medium for creating a lock manager data structure in volatile memory for an object assigned a distributed lock obtained from a server;
means in the medium for assigning an identifying number to a file system in which said object is located;
means in the medium for incrementing said file system identifying number upon a restart of said server assigned to said file system;
means in the medium for comparing a file system identifying number provided by a client requesting a lock on said system object with a current file system identifying number in which said object is located; and
means in the medium for granting a lock reassertion request to said requesting client subsequent to breaking a lock if said compared file system identifying numbers are within an appropriate range.
14. The article of claim 13 , wherein the medium is selected from a group consisting of: a recordable data storage medium and a modulated carrier signal.
15. The article of claim 13 , further comprising means in the medium for restoring cache consistency between a client and said server in conjunction with a reassert of a lock request from said client subsequent to loss of a lock lease.
16. The article of claim 15 , wherein said means for restoring cache consistency includes a cache manager adapted to merge client attributes with server node attributes.
17. The article of claim 13 , further comprising means in the medium for deferring commitment of a new filesystem identifying number in persistent storage until expiration of a lock reassertion grace period.
18. The article of claim 13 , further comprising means in the medium for notifying a client of theft of a lock on which said client possesses a compatible lock.
19. The article of claim 13 , wherein said data structure includes data selected from a group consisting of: a list of locks held by each client node, a lock mode for each lock, a state of any pending demands, and a set of lock modes granted on an object.