US20050289143A1 - Method for managing lock resources in a distributed storage system - Google Patents
Method for managing lock resources in a distributed storage system Download PDFInfo
- Publication number
- US20050289143A1 US20050289143A1 US11/159,216 US15921605A US2005289143A1 US 20050289143 A1 US20050289143 A1 US 20050289143A1 US 15921605 A US15921605 A US 15921605A US 2005289143 A1 US2005289143 A1 US 2005289143A1
- Authority
- US
- United States
- Prior art keywords
- lock
- request
- file
- convert
- lock request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F17/00—Digital computing or data processing equipment or methods, specially adapted for specific functions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/176—Support for shared access to files; File sharing support
- G06F16/1767—Concurrency control, e.g. optimistic or pessimistic approaches
- G06F16/1774—Locking methods, e.g. locking methods for file systems allowing shared and concurrent access to files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
Definitions
- the present invention relates generally to distributed file systems, and more particularly, for managing lock resources in distributed file systems.
- distributed storage systems implement distributed architectures, i.e., distributed storage systems.
- processing nodes e.g., storage servers
- client applications characterize a distributed storage system.
- the processing nodes and systems that host the client applications are connected through a network.
- the system 100 comprises of a plurality of independent processing nodes 110 connected to storage devices 120 through a Fiber Channel (FC) connection 130 .
- a storage device 120 may be a tape drive, a disk drive, a redundant array of independent disks (RAID) or similar devices.
- the processing nodes 110 are further connected to a plurality of clients 140 through a gigabit Ethernet or InfiBand connection 150 .
- the clients 140 may utilize any file sharing protocols, such as network file system (NFS), common internet file system (CIFS), direct access file system (DAFS) or AppleShare to access data stored in storage devices 120 .
- NFS network file system
- CIFS common internet file system
- DAFS direct access file system
- AppleShare AppleShare
- the processing nodes 110 communicate through a network 160 , which may be a dedicated network, a wide area network (WAN), a metropolitan area network (MAN) or a local area network (LAN).
- a network 160 may be a dedicated network, a wide area network (WAN), a metropolitan area network (MAN) or a local area network (LAN).
- WAN wide area network
- MAN metropolitan area network
- LAN local area network
- the operation of the system 100 is managed by a distributed file system allows for sharing and storing files in the storage devices 120 or in a cache memory on various levels of storage hierarchy. Additionally, the distributed file system provides a locking mechanism to maintain data consistency of shared files. Specifically, the locking mechanism guarantees that only one client can write to a single file at a time. For example, when a client 140 - 1 writes to a file “A”, the file is locked to prevent another client 140 - 2 from manipulating the file “A”. When client 140 - 1 closes file “A” and client 140 - 2 attempts to write to that file, the distributed file system then informs client 140 - 2 that changes were made to the file “A”.
- client 140 can access a file using a plurality of file sharing protocols, each such protocol providing a different mechanism for locking files.
- the NFS protocol supports share locks and byte range locks
- the CIFS protocol supports share locks and byte range locks, as well as the opportunistic locks (Oplocks).
- a share lock provides exclusive or non-exclusive access permission for an entire file
- the byte range lock provides the same permission for a portion of a file.
- the Oplock is a non-persistent mechanism that is designed for optimizing local file caching.
- the Oplock allows a client 140 to notify a processing node 110 that another client (or process) requires access to the file and as result client 140 should flush the cached file back to the server.
- an exclusive lock granted to a client 140 does not allow other clients to access the file.
- a non-exclusive lock granted to a client 140 allows other clients to access the file for reading from or writing to the file. The access rights depend on the lock's mode.
- Illustrative, non-limiting embodiments of the present invention overcome the above disadvantages and other disadvantages not described above. Also, the present invention is not required to overcome the disadvantages described above, and an illustrative, non-limiting embodiment of the present invention may not overcome any of the problems described above.
- a first aspect of the present invention provides a method for managing file locks in a distributed storage system by providing a plurality of registry lock files maintained by a plurality of locking managers, wherein each of the registry lock files comprises a list of locked files and a list of lock requests.
- the method provides a plurality of lock resource objects, wherein each of the plurality of lock resource objects is allocated to a lockable file.
- the method services a client lock request based on the information maintained by the lock resource objects and the registry lock files.
- the registry lock file comprises a unique identification of the client requesting the lock and a host name of the client, and the list of files contains files locked by the client requesting the lock in a domain of the locking manager.
- the list of files also contains a file name of the locked file and a counter recording the number of requested locks for the locked file.
- each of the lock resource objects is part of metadata of the lockable file.
- each of the lock resource objects comprises at least a block queue, a convert queue, a grant list and a wakeup list.
- the block queue comprises lock requests that are not granted.
- the convert queue comprises granted lock requests attempting to change lock modes.
- the grant list comprises lock requests granted by the lock resource object, and the wakeup list comprises blocked lock requests with limited time duration.
- servicing a client lock request comprises receiving a new lock request from the client to lock a file, forwarding the lock request to a lock manager that belongs to the same domain to which the file to be locked belongs to and writing the lock request to the registry lock file maintained by the lock manager.
- the lock request is blocked if the convert queue or the block queue comprises at least one lock request, and the lock request is blocked if it is in conflict with an already granted lock saved in the grant list. Otherwise, the lock request is granted.
- Blocking the lock request comprises inserting the lock request into the lock queue, inserting the lock request into the wakeup list if the lock request comprises a timeout parameter and sending a message that the lock request is blocked.
- the granting of a lock request comprises inserting the lock request into the grant queue and sending a message that the convert lock that request is granted.
- servicing of the lock request comprises receiving a convert lock request to change the mode of the lock, searching in the registry lock file for a lock request associated with the convert lock request and blocking the convert lock request if at least the convert queue is not empty and/or the requested mode is not compatible with a most restrictive mode of a currently granted lock. Otherwise, the lock request is granted.
- Blocking the convert lock request further comprises changing the mode of the lock request associated with the convert lock request, inserting the lock request into the convert queue and sending a message that the convert lock request is blocked.
- Granting the convert lock request comprises changing the mode of the lock request associated with the convert lock request, inserting the lock request into the grant list and sending a message that the convert lock request is granted.
- a second aspect of the present invention provides a computer program product for enabling a computer to managing file locks in a distributed storage system comprising software instructions for enabling the computer to perform predetermined operations, and a computer readable medium bearing the software instructions.
- the predetermined operations comprise providing a plurality of registry lock files maintained by a plurality of locking managers, wherein each of the registry lock files comprises a list of locked files and a list of lock requests.
- the predetermined operations provide a plurality of lock resource objects, wherein each of the plurality of lock resource objects is allocated to a lockable file.
- the predetermined operations service a client lock request based on the information maintained by the lock resource objects and the registry lock files.
- the registry lock file comprises a unique identification of the client requesting the lock and a host name of the client, and the list of files contains files locked by the client requesting the lock in a domain of the locking manager.
- the list of files also contains a file name of the locked file and a counter recording the number of requested locks for the locked file.
- each of the lock resource objects is part of metadata of the lockable file.
- each of the lock resource objects comprises at least a block queue, a convert queue, a grant list and a wakeup list.
- the block queue comprises lock requests that are not granted.
- the convert queue comprises granted lock requests attempting to change lock modes.
- the grant list comprises lock requests granted by the lock resource object, and the wakeup list comprises blocked lock requests with limited time duration.
- the predetermined operations service a client lock request by receiving a new lock request from the client to lock a file, forwarding the lock request to a lock manager that belongs to the same domain to which the file to be locked belongs to and writing the lock request to the registry lock file maintained by the lock manager.
- the predetermined operations block the lock request if the convert queue or the block queue comprises at least one lock request, and the predetermined operations block the lock request if it is in conflict with an already granted lock saved in the grant list. Otherwise, the predetermined operations grant the lock request.
- the predetermined operations block a lock request by inserting the lock request into the lock queue, inserting the lock request into the wakeup list if the lock request comprises a timeout parameter and sending a message that the lock request is blocked.
- the predetermined operations grant a lock request by inserting the lock request into the grant queue and sending a message that the convert lock that request is granted.
- the predetermined operations service a lock request by receiving a convert lock request to change the mode of the lock, searching in the registry lock file for a lock request associated with the convert lock request and blocking the convert lock request if at least the convert queue is not empty and/or the requested mode is not compatible with a most restrictive mode of a currently granted lock. Otherwise, the predetermined operations grant a lock request.
- the predetermined operations block the convert lock request by changing the mode of the lock request associated with the convert lock request, inserting the lock request into the convert queue and sending a message that the convert lock request is blocked.
- the predetermined operations grant the convert lock request by changing the mode of the lock request associated with the convert lock request, inserting the lock request into the grant list and sending a message that the convert lock request is granted.
- a third aspect of the present invention provides a distributed lock system for managing lock resources in a distributed storage system.
- the distributed lock system comprises a plurality of locking managers, wherein each of the plurality of locking managers is capable of managing lock resources in its respective domain.
- the system further comprises a plurality of metadata servers capable of maintaining a plurality of a lock resource objects, and a central database for maintaining locking information.
- Each of the plurality of lock resource objects is part of metadata of the lockable file.
- the locking information comprises a plurality of registry lock files, wherein each of the plurality registry lock files comprises at least a list of locked files and a list of lock requests.
- Each of the plurality of lock resource objects is allocated to a lockable file.
- the registry lock file comprises a unique identification of the client requesting the lock and a host name of the client.
- the list of files contains files locked by the client requesting the lock in a domain of the locking manager, and the list of files includes at least a file name of the locked file and a counter recording a number of requested locks for the locked file.
- Each of the plurality of lock resource objects comprises a block queue, a convert queue, a grant list and a wakeup list.
- the block queue comprises lock requests that are not granted.
- the convert queue comprises granted lock requests attempting to change lock modes.
- the grant list comprises lock requests granted by the lock resource object.
- the wakeup list comprises blocked lock requests with limited time duration.
- FIG. 1 is an exemplary diagram of a conventional distributed storage system
- FIG. 2 is a diagram of a distributed locking system according to an exemplary embodiment of the present invention.
- FIG. 3 is an illustration of a registry lock file according to an exemplary embodiment of the present invention.
- FIG. 4 is an illustration of a lock resource object according to an exemplary embodiment of the present invention.
- FIG. 5 is a flowchart describing the method for handling a new lock request according to an exemplary embodiment of the present invention
- FIG. 6 is a flowchart describing the step for blocking a lock request according to an exemplary embodiment of the present invention.
- FIG. 7 is a flowchart describing the method for handling a convert lock request according to an exemplary embodiment of the present invention.
- the DLS 200 comprises a plurality of locking managers (LMs) 220 - 1 , 220 - 2 , 220 - n connecting to a central database 230 that maintains the locking information.
- LMs locking managers
- Each of the LMs 220 - 1 , 220 - 2 , 220 - n is further connected to a client interface 210 - 1 , 210 - 2 , 210 - n and a metadata (MD) server 250 - 1 , 250 - 2 , 250 - n .
- MD metadata
- the client interface 210 - 1 , 210 - 2 , 210 - n is responsible for receiving requests from a client 240 - 1 , 240 - m and handling the interface with a LM 220 - 1 , 220 - 2 , 220 - n (among other components a distributed file system that are not despite in FIG. 2 ).
- the client interface 210 - 1 , 210 - 2 , 210 - n acts as a protocol converter, translating between client-side protocols (e.g., NFS, CIFS, AppleTalk, etc.) and internal file system requests, such as remote procedure call (RPC) requests.
- client-side protocols e.g., NFS, CIFS, AppleTalk, etc.
- RPC remote procedure call
- the MD server 250 - 1 , 250 - 2 , 250 - n maintains the metadata information or objects of a file, relative to files are located.
- the metadata information in MD server 250 - 1 , 250 - 2 , 250 - n may include, but is not limited to, file name, its type, its permissions, ownership and other type of information other than the content of the file.
- the MD server 250 - 1 , 250 - 2 , 250 - n further maintains as part of the metadata information a lock resource (LR) object assigned for each locked file.
- LR lock resource
- the client interface 210 - 1 , 210 - 2 , 210 - n , the LM 220 - 1 , 220 - 2 , 220 - n and the MD server 250 - 1 , 250 - 2 , 250 - n may coexist on a single processing node (e.g., node 110 ).
- the content of the database 230 is distributed over the processing nodes.
- Each LM 220 - 1 , 220 - 2 , 220 - n manages the lock requests of files belonging to its domain (i.e., address space) using a plurality of LR objects and the plurality of registry lock files of the plurality of LMs 220 - 1 , 220 - 2 , 220 - n are kept in the database 230 .
- a registry lock file comprises a list of locked files in the domain of a LM 220 - 1 , 220 - 2 , 220 - n . Specifically, as shown in FIG.
- a lock file 300 comprises the unique identification (ID) of the client requesting the lock, the client's host name and a list of files 320 locked by the requesting client (hereinafter the “locked file list”).
- Each entry in the locked file list 320 comprises the file name of the locked file and a counter counting the number of requested locks for that file. The counter is incremented each time a new lock is added and decremented each time a lock is removed.
- the registry lock file 300 further comprises a list of lock requests 310 per each client (hereinafter the “lock request list”).
- the lock request list 310 comprises the client unique ID, the client's host name, a request unique ID, the request creation time and the status of the request, i.e., blocked, converted, or granted.
- the registry lock file 300 may be implemented using a balanced tree indexes (e.g., B-tree indexes).
- each record in the registry lock file 300 comprises the host name and the requesting client's unique identification (ID) represented in the following notation host_index@domian.client_index and the name of an index file containing the locked file list 320 of the client under the domain designated in host_index@domian.client_index.
- ID unique identification
- a LR object is allocated per a lockable entity once a client 240 - 1 , 240 - m requests to lock this entity.
- a lockable entity may be a file, a portion of a file or any object stored in the physical storage of a distributed storage system.
- the LM 220 - 1 , 220 - 2 , 220 - n manages the lock requests using a plurality of LR objects.
- An exemplary LR object 400 is shown in FIG. 4 .
- the LR object 400 maintains a block queue 410 , a convert queue 420 , a grant list 430 and a wakeup list 440 .
- the block queue 410 contains new requests that are not granted, as these requests are in conflict with a currently granted lock saved in grant list 430 .
- the convert queue 420 contains granted requests that attempt to upgrade or downgrade their lock modes, which are incompatible with the mode of the currently granted lock.
- the grant list 430 contains all locks granted by the LM 220 - 1 , 220 - 2 , 220 - n on the LR object 400 .
- Each request in the block queue 410 , the convert queue 420 and the grant list 430 comprises a lock request unique ID, its request creation time and a pointer to the corresponding lock request list 310 in the registry lock file 300 .
- the wakeup list 440 maintains blocked lock requests that include a timeout parameter.
- the timeout parameter defines the duration of the request, i.e., the maximum time that a request waits on a blocked lock.
- a blocked request is a request that cannot be granted due to a conflict with an already granted lock or locks.
- a blocked request is inserted to the block queue 410 of the LR object 400 .
- the request is removed from the block queue 410 only if the following conditions are satisfied: a) the request's mode is compatible with the most restrictive mode of locks kept in the grant list 430 ; b) the convert queue 420 is empty; and c) the request lock is at the head of the block queue 410 .
- a converted request is a dissatisfied request of the client 240 - 1 , 240 - m to change the lock's current mode.
- the client 240 - 1 , 240 - m can request to upgrade the lock's mode, i.e., to change the mode from a non-exclusive to exclusive mode or to downgrade the lock's mode, i.e., to change the mode from an exclusive to non-exclusive mode.
- a converted request is saved in the convert queue 420 .
- the LM 220 - 1 , 220 - 2 , 220 - n grants all demote requests in-place, namely the lock is downgraded to its new mode without being inserted to the convert queue 420 .
- a granted request is a request that was granted.
- the LM 220 - 1 , 220 - 2 , 220 - n grants a lock request if there are currently no locks on the files requested to be locked, i.e., the grant list 430 is empty or if the convert queue 420 is empty and the lock request's mode is compatible with the most restrictive mode of the currently granted lock. All granted locks on the LR 400 are saved in the grant list 430 .
- the methods for handling a new lock request and a convert request are described in greater detail below.
- a client 240 - 1 sends a lock request R 1 to the LM 220 - 1 to lock a file “B”.
- the lock's mode of request R 1 is exclusive, i.e., deny other clients access to file “B”.
- File “B” is kept in the domain of the LM 220 - 2 .
- a lock request comprises the client unique ID, the client's host name, and the client process ID.
- the LM 220 - 1 upon receiving request R 1 , replaces the client unique ID and client's host name with a host index and a client index using the following notation host_index@domain.client_index.
- the LM 220 - 1 checks if a LR object assigned to file “B” belongs to its domain; since it does not, the LM 220 - 1 forwards the request R 1 to the LM 220 - 2 .
- the LM 220 - 2 saves the request R 1 in its registry lock file in the database 230 and detects a LR object in the MD server 250 - 2 assigned to file “B”. If such a LR object does not exist, the LM 220 - 1 allocates a new LR object. It should be noted that while modifying the registry lock file, the database 230 is locked. This is performed in order to ensure data consistency. Subsequently, the LM 220 - 2 checks if the request R 1 can be granted.
- the file is locked and the lock request is saved in the grant list 430 and its status is updated to a granted state.
- the lock of file “B” holds exclusive rights, all subsequent lock requests on file “B” with non-exclusive lock's mode will be denied.
- the client 240 - 1 must send a convert request to change the lock's mode on file “B” from exclusive to non-exclusive or a request to remove the lock.
- the LM 220 - 2 replies to the client 240 - 1 with a message notifying that the lock request is denied and then the lock request in saved in the block queue 410 .
- a non-limiting flowchart 500 describing the method for handling a new lock request is shown.
- the method is executed by a LM (e.g., LM 220 - 1 ) belonging to the same domain as that of the file requested to be locked.
- the type of the lock request may be handled by, but is not limited to, a share lock, a byte range lock, an Oplock and other lock schemes.
- a new lock request received at a LM acquires a unique ID.
- the database 230 is locked for preventing other clients to write to the database 230 and the new request's parameters are saved in the in the registry lock file (e.g., registry lock file 300 ) corresponds to the LM that received the request.
- the request parameters comprise a client unique ID (or a client index), a host name (or a host index), a request unique ID, and the request creation time.
- the database 230 is unlocked.
- a check is made to determine if the convert queue is empty, and if so, execution continues with S 540 ; otherwise, the execution continues at S 580 where the request is blocked.
- a check is performed to determine if the block queue is empty and if so the execution continues with S 550 ; otherwise, the execution continues with S 580 .
- another check is made to determine if the request can be satisfied. Specifically, it is checked whether the lock request is in conflict with an already granted lock saved in the grant list. If the request can be satisfied, at S 560 , the lock's status in the registry lock file is updated to a granted state and the request is added to the grant list.
- a message is send to the client notifying the lock request is granted. If the lock request is denied, the execution continues with S 580 .
- a detailed flowchart describing the blocking of a request (S 580 ) is shown.
- the request status in the registry lock file is set to a blocked mode.
- the request is added to the block queue.
- the request and its wakeup time are saved in the wakeup list.
- S 630 is performed only if the request comprises a timeout parameter, which defines the duration time of the request. The duration time defines the amount of time that a lock request waits to a lock to be unlocked.
- a message is sent to the requesting client notifying that the lock request is blocked.
- a non-limiting flowchart 700 describing the method for handling a convert request is shown.
- the method is executed by a LM (e.g., LM 220 - 1 ) belonging to the same domain as that of the file being locked.
- the type of the lock request to be handled may be, but is not limited to, a share lock, a byte range lock, an Oplock and other lock schemes.
- a client can request to upgrade the lock's mode, i.e., to change lock's mode from a non-exclusive to exclusive mode or to downgrade the lock's mode, i.e., to change the mode from an exclusive to non-exclusive mode.
- a new convert request is received at a LM.
- the convert request comprises the client unique ID (or client index), client's host name (or host index) and the lock ID of the lock to be converted.
- the lock request list e.g., list 310
- the registry lock file e.g., registry lock file 300
- the search is made using the lock's unique ID.
- a check is made to determine if a lock having the same lock ID as designated in the request is found, and if so the execution continues with S 740 ; otherwise, the request is denied and execution ends.
- a request for converting the mode of a non-granted lock is also denied.
- a check is made to determine if the convert queue 420 is empty, and if so execution continues at S 760 ; otherwise, execution continues with S 750 where the lock's mode is changed to the new requested mode.
- the status of the lock is set to converted state and the lock is added to the convert queue 420 .
- a check is made to determine if the convert lock request can be satisfied. Specifically, it is checked whether the requested mode is compatible with the most restrictive mode of the currently granted lock. If the request is satisfied, then at S 770 , the lock's status is set to a granted state and the lock is added to the grant list.
- the lock status is set to a converted state and the lock is added to the convert queue 420 .
- the request and its wakeup time are saved in the wakeup list 440 .
- S 785 is performed only if the request comprises a timeout parameter.
- a message is sent to the requesting client notifying the request is denied.
- the method and the DLS disclosed herein can be operated in a mixed mode, namely to handle concurrently lock requests utilized through different file sharing protocols.
- Each protocol defines its own requirements to impose a lock on a file.
- These different requirements of the lock mode should be addressed by the DLS 200 while operating is a mixed mode.
- the CIFS protocol requires that file byte range locks be granted only after a share lock is granted on the file, while in the NFS protocol only byte range locks can be used.
- NFS requests are byte range lock requests
- a share lock entry for each client is created. Specifically, a first byte range lock request from a client creates a share lock request. If the share lock is compatible with currently granted locks this request will be satisfied. After granting a share lock on the file, the requested byte range is locked. The restrictive mode of the byte range lock is the mode of the share lock on the locked file.
- the DLS and the methods for handling the lock requests disclosed herein can be operated in conjunction with a distributed shared files system (DSFS) disclosed in U.S. patent application Ser. No. 10/265,778, entitled “Flexible and Adaptive Read and Write Storage System Architecture” assigned to common assignee and which is hereby incorporated by reference for all that it contains.
- DSFS distributed shared files system
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Mathematical Physics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
- This application claims priority from U.S. Provisional Patent Application No. 60/581,721, filed Jun. 23, 2004, the disclosure of which is incorporated herein in its entirety by reference.
- The present invention relates generally to distributed file systems, and more particularly, for managing lock resources in distributed file systems.
- During the past decade, the demand for scalability of storage systems has sharply increased. To meet this demand many storage systems implement distributed architectures, i.e., distributed storage systems. Generally, multiple processing nodes (e.g., storage servers) that serve data to client applications characterize a distributed storage system. The processing nodes and systems that host the client applications are connected through a network.
- Referring to
FIG. 1 , an exemplary diagram of adistributed storage system 100 is shown. Thesystem 100 comprises of a plurality ofindependent processing nodes 110 connected tostorage devices 120 through a Fiber Channel (FC)connection 130. Astorage device 120 may be a tape drive, a disk drive, a redundant array of independent disks (RAID) or similar devices. Theprocessing nodes 110 are further connected to a plurality ofclients 140 through a gigabit Ethernet or InfiBandconnection 150. Theclients 140 may utilize any file sharing protocols, such as network file system (NFS), common internet file system (CIFS), direct access file system (DAFS) or AppleShare to access data stored instorage devices 120. Theprocessing nodes 110 communicate through anetwork 160, which may be a dedicated network, a wide area network (WAN), a metropolitan area network (MAN) or a local area network (LAN). This allowsdistributed storage system 100 to aggregate dispersed data centers into a single, unified, storage device. An example of adistributed storage system 100 is disclosed in PCT patent application PCT/US00/34258, entitled “Interconnect Topology for a Scalable Distributed Computer System” assigned to common assignee and which is hereby incorporated by reference for all that it discloses. - The operation of the
system 100 is managed by a distributed file system allows for sharing and storing files in thestorage devices 120 or in a cache memory on various levels of storage hierarchy. Additionally, the distributed file system provides a locking mechanism to maintain data consistency of shared files. Specifically, the locking mechanism guarantees that only one client can write to a single file at a time. For example, when a client 140-1 writes to a file “A”, the file is locked to prevent another client 140-2 from manipulating the file “A”. When client 140-1 closes file “A” and client 140-2 attempts to write to that file, the distributed file system then informs client 140-2 that changes were made to the file “A”. - As mentioned above,
client 140 can access a file using a plurality of file sharing protocols, each such protocol providing a different mechanism for locking files. For example, the NFS protocol supports share locks and byte range locks, whereas the CIFS protocol supports share locks and byte range locks, as well as the opportunistic locks (Oplocks). A share lock provides exclusive or non-exclusive access permission for an entire file, while the byte range lock provides the same permission for a portion of a file. The Oplock is a non-persistent mechanism that is designed for optimizing local file caching. The Oplock allows aclient 140 to notify aprocessing node 110 that another client (or process) requires access to the file and asresult client 140 should flush the cached file back to the server. Generally, an exclusive lock granted to aclient 140 does not allow other clients to access the file. A non-exclusive lock granted to aclient 140 allows other clients to access the file for reading from or writing to the file. The access rights depend on the lock's mode. - In related art, distributed file mechanisms are disclosed in U.S. Pat. Nos. 5,828,876, 6,009,427 and 6,173,293. However, the disclosed mechanisms do not provide locking services satisfying the locking requirements of all file-sharing protocols. Specifically, the current locking mechanisms do not enable simultaneous operations of different sharing protocols on the same file system resource. Furthermore, the distributed locking mechanisms disclosed in the related are not scalable beyond a certain number of nodes.
- Therefore, it would be advantageous to provide a method and a distributed locking system that would resolve the shortcomings introduced in by the prior art.
- Illustrative, non-limiting embodiments of the present invention overcome the above disadvantages and other disadvantages not described above. Also, the present invention is not required to overcome the disadvantages described above, and an illustrative, non-limiting embodiment of the present invention may not overcome any of the problems described above.
- A first aspect of the present invention provides a method for managing file locks in a distributed storage system by providing a plurality of registry lock files maintained by a plurality of locking managers, wherein each of the registry lock files comprises a list of locked files and a list of lock requests. Next, the method provides a plurality of lock resource objects, wherein each of the plurality of lock resource objects is allocated to a lockable file. Finally, the method services a client lock request based on the information maintained by the lock resource objects and the registry lock files. The registry lock file comprises a unique identification of the client requesting the lock and a host name of the client, and the list of files contains files locked by the client requesting the lock in a domain of the locking manager. The list of files also contains a file name of the locked file and a counter recording the number of requested locks for the locked file.
- In the present invention, each of the lock resource objects is part of metadata of the lockable file. In addition, each of the lock resource objects comprises at least a block queue, a convert queue, a grant list and a wakeup list. The block queue comprises lock requests that are not granted. The convert queue comprises granted lock requests attempting to change lock modes. The grant list comprises lock requests granted by the lock resource object, and the wakeup list comprises blocked lock requests with limited time duration.
- Servicing a client lock request comprises receiving a new lock request from the client to lock a file, forwarding the lock request to a lock manager that belongs to the same domain to which the file to be locked belongs to and writing the lock request to the registry lock file maintained by the lock manager. The lock request is blocked if the convert queue or the block queue comprises at least one lock request, and the lock request is blocked if it is in conflict with an already granted lock saved in the grant list. Otherwise, the lock request is granted. Blocking the lock request comprises inserting the lock request into the lock queue, inserting the lock request into the wakeup list if the lock request comprises a timeout parameter and sending a message that the lock request is blocked. The granting of a lock request comprises inserting the lock request into the grant queue and sending a message that the convert lock that request is granted.
- In the alternative, servicing of the lock request comprises receiving a convert lock request to change the mode of the lock, searching in the registry lock file for a lock request associated with the convert lock request and blocking the convert lock request if at least the convert queue is not empty and/or the requested mode is not compatible with a most restrictive mode of a currently granted lock. Otherwise, the lock request is granted. Blocking the convert lock request further comprises changing the mode of the lock request associated with the convert lock request, inserting the lock request into the convert queue and sending a message that the convert lock request is blocked. Granting the convert lock request comprises changing the mode of the lock request associated with the convert lock request, inserting the lock request into the grant list and sending a message that the convert lock request is granted.
- A second aspect of the present invention provides a computer program product for enabling a computer to managing file locks in a distributed storage system comprising software instructions for enabling the computer to perform predetermined operations, and a computer readable medium bearing the software instructions. The predetermined operations comprise providing a plurality of registry lock files maintained by a plurality of locking managers, wherein each of the registry lock files comprises a list of locked files and a list of lock requests. Next, the predetermined operations provide a plurality of lock resource objects, wherein each of the plurality of lock resource objects is allocated to a lockable file. Finally, the predetermined operations service a client lock request based on the information maintained by the lock resource objects and the registry lock files. The registry lock file comprises a unique identification of the client requesting the lock and a host name of the client, and the list of files contains files locked by the client requesting the lock in a domain of the locking manager. The list of files also contains a file name of the locked file and a counter recording the number of requested locks for the locked file.
- In the present invention, each of the lock resource objects is part of metadata of the lockable file. In addition, each of the lock resource objects comprises at least a block queue, a convert queue, a grant list and a wakeup list. The block queue comprises lock requests that are not granted. The convert queue comprises granted lock requests attempting to change lock modes. The grant list comprises lock requests granted by the lock resource object, and the wakeup list comprises blocked lock requests with limited time duration.
- The predetermined operations service a client lock request by receiving a new lock request from the client to lock a file, forwarding the lock request to a lock manager that belongs to the same domain to which the file to be locked belongs to and writing the lock request to the registry lock file maintained by the lock manager. The predetermined operations block the lock request if the convert queue or the block queue comprises at least one lock request, and the predetermined operations block the lock request if it is in conflict with an already granted lock saved in the grant list. Otherwise, the predetermined operations grant the lock request. The predetermined operations block a lock request by inserting the lock request into the lock queue, inserting the lock request into the wakeup list if the lock request comprises a timeout parameter and sending a message that the lock request is blocked. The predetermined operations grant a lock request by inserting the lock request into the grant queue and sending a message that the convert lock that request is granted.
- In the alternative, the predetermined operations service a lock request by receiving a convert lock request to change the mode of the lock, searching in the registry lock file for a lock request associated with the convert lock request and blocking the convert lock request if at least the convert queue is not empty and/or the requested mode is not compatible with a most restrictive mode of a currently granted lock. Otherwise, the predetermined operations grant a lock request. The predetermined operations block the convert lock request by changing the mode of the lock request associated with the convert lock request, inserting the lock request into the convert queue and sending a message that the convert lock request is blocked. The predetermined operations grant the convert lock request by changing the mode of the lock request associated with the convert lock request, inserting the lock request into the grant list and sending a message that the convert lock request is granted.
- A third aspect of the present invention provides a distributed lock system for managing lock resources in a distributed storage system. The distributed lock system comprises a plurality of locking managers, wherein each of the plurality of locking managers is capable of managing lock resources in its respective domain. The system further comprises a plurality of metadata servers capable of maintaining a plurality of a lock resource objects, and a central database for maintaining locking information. Each of the plurality of lock resource objects is part of metadata of the lockable file. The locking information comprises a plurality of registry lock files, wherein each of the plurality registry lock files comprises at least a list of locked files and a list of lock requests. Each of the plurality of lock resource objects is allocated to a lockable file. The registry lock file comprises a unique identification of the client requesting the lock and a host name of the client. The list of files contains files locked by the client requesting the lock in a domain of the locking manager, and the list of files includes at least a file name of the locked file and a counter recording a number of requested locks for the locked file.
- Each of the plurality of lock resource objects comprises a block queue, a convert queue, a grant list and a wakeup list. The block queue comprises lock requests that are not granted. The convert queue comprises granted lock requests attempting to change lock modes. The grant list comprises lock requests granted by the lock resource object. The wakeup list comprises blocked lock requests with limited time duration.
- Additional aspects and/or advantages of the invention will be set forth in part in the description that follows and, in part, will be apparent from the description, or may be learned by practice of the invention.
- The accompanying drawings, which are incorporated in and constitute a part of this specification illustrate exemplary embodiments of the invention and, together with the description, serve to explain the aspects, advantages and principles of the invention. In the drawings,
-
FIG. 1 is an exemplary diagram of a conventional distributed storage system; -
FIG. 2 is a diagram of a distributed locking system according to an exemplary embodiment of the present invention; -
FIG. 3 is an illustration of a registry lock file according to an exemplary embodiment of the present invention; -
FIG. 4 is an illustration of a lock resource object according to an exemplary embodiment of the present invention; -
FIG. 5 is a flowchart describing the method for handling a new lock request according to an exemplary embodiment of the present invention; -
FIG. 6 is a flowchart describing the step for blocking a lock request according to an exemplary embodiment of the present invention; and -
FIG. 7 is a flowchart describing the method for handling a convert lock request according to an exemplary embodiment of the present invention. - The present invention will now be described more fully with reference to the accompanying drawings, in which exemplary, non-limiting embodiments of the invention are shown.
- Referring to
FIG. 2 , an exemplary and non-limiting diagram of a distributed locking system (DLS) 200 in accordance with the present invention is shown. TheDLS 200 comprises a plurality of locking managers (LMs) 220-1, 220-2, 220-n connecting to acentral database 230 that maintains the locking information. Each of the LMs 220-1, 220-2, 220-n is further connected to a client interface 210-1, 210-2, 210-n and a metadata (MD) server 250-1, 250-2, 250-n. The client interface 210-1, 210-2, 210-n is responsible for receiving requests from a client 240-1, 240-m and handling the interface with a LM 220-1, 220-2, 220-n (among other components a distributed file system that are not despite inFIG. 2 ). In essence, the client interface 210-1, 210-2, 210-n acts as a protocol converter, translating between client-side protocols (e.g., NFS, CIFS, AppleTalk, etc.) and internal file system requests, such as remote procedure call (RPC) requests. The MD server 250-1, 250-2, 250-n maintains the metadata information or objects of a file, relative to files are located. The metadata information in MD server 250-1, 250-2, 250-n may include, but is not limited to, file name, its type, its permissions, ownership and other type of information other than the content of the file. The MD server 250-1, 250-2, 250-n further maintains as part of the metadata information a lock resource (LR) object assigned for each locked file. The structure and the functionality of the LR objects will be described in greater detail below. The client interface 210-1, 210-2, 210-n, the LM 220-1, 220-2, 220-n and the MD server 250-1, 250-2, 250-n may coexist on a single processing node (e.g., node 110). The content of thedatabase 230 is distributed over the processing nodes. - Each LM 220-1, 220-2, 220-n manages the lock requests of files belonging to its domain (i.e., address space) using a plurality of LR objects and the plurality of registry lock files of the plurality of LMs 220-1, 220-2, 220-n are kept in the
database 230. A registry lock file comprises a list of locked files in the domain of a LM 220-1, 220-2, 220-n. Specifically, as shown inFIG. 3 , alock file 300 comprises the unique identification (ID) of the client requesting the lock, the client's host name and a list offiles 320 locked by the requesting client (hereinafter the “locked file list”). Each entry in the lockedfile list 320 comprises the file name of the locked file and a counter counting the number of requested locks for that file. The counter is incremented each time a new lock is added and decremented each time a lock is removed. Theregistry lock file 300 further comprises a list of lock requests 310 per each client (hereinafter the “lock request list”). The lock request list 310 comprises the client unique ID, the client's host name, a request unique ID, the request creation time and the status of the request, i.e., blocked, converted, or granted. - In an exemplary embodiment of the present invention, the
registry lock file 300 may be implemented using a balanced tree indexes (e.g., B-tree indexes). In this exemplary embodiment, each record in theregistry lock file 300 comprises the host name and the requesting client's unique identification (ID) represented in the following notation host_index@domian.client_index and the name of an index file containing the lockedfile list 320 of the client under the domain designated in host_index@domian.client_index. - A LR object is allocated per a lockable entity once a client 240-1, 240-m requests to lock this entity. A lockable entity may be a file, a portion of a file or any object stored in the physical storage of a distributed storage system. The LM 220-1, 220-2, 220-n manages the lock requests using a plurality of LR objects. An
exemplary LR object 400 is shown inFIG. 4 . The LR object 400 maintains ablock queue 410, aconvert queue 420, agrant list 430 and awakeup list 440. Theblock queue 410 contains new requests that are not granted, as these requests are in conflict with a currently granted lock saved ingrant list 430. Theconvert queue 420 contains granted requests that attempt to upgrade or downgrade their lock modes, which are incompatible with the mode of the currently granted lock. Thegrant list 430 contains all locks granted by the LM 220-1, 220-2, 220-n on theLR object 400. Each request in theblock queue 410, theconvert queue 420 and thegrant list 430 comprises a lock request unique ID, its request creation time and a pointer to the corresponding lock request list 310 in theregistry lock file 300. Thewakeup list 440 maintains blocked lock requests that include a timeout parameter. The timeout parameter defines the duration of the request, i.e., the maximum time that a request waits on a blocked lock. - As discussed above, the status of each incoming lock request can be set to be one of blocked, converted or granted. A blocked request is a request that cannot be granted due to a conflict with an already granted lock or locks. A blocked request is inserted to the
block queue 410 of theLR object 400. The request is removed from theblock queue 410 only if the following conditions are satisfied: a) the request's mode is compatible with the most restrictive mode of locks kept in thegrant list 430; b) theconvert queue 420 is empty; and c) the request lock is at the head of theblock queue 410. A converted request is a dissatisfied request of the client 240-1, 240-m to change the lock's current mode. The client 240-1, 240-m can request to upgrade the lock's mode, i.e., to change the mode from a non-exclusive to exclusive mode or to downgrade the lock's mode, i.e., to change the mode from an exclusive to non-exclusive mode. A converted request is saved in theconvert queue 420. The LM 220-1, 220-2, 220-n grants all demote requests in-place, namely the lock is downgraded to its new mode without being inserted to theconvert queue 420. A granted request is a request that was granted. The LM 220-1, 220-2, 220-n grants a lock request if there are currently no locks on the files requested to be locked, i.e., thegrant list 430 is empty or if theconvert queue 420 is empty and the lock request's mode is compatible with the most restrictive mode of the currently granted lock. All granted locks on theLR 400 are saved in thegrant list 430. The methods for handling a new lock request and a convert request are described in greater detail below. - The following is an example describing the operation of the
DLS 200. A client 240-1 sends a lock request R1 to the LM 220-1 to lock a file “B”. The lock's mode of request R1 is exclusive, i.e., deny other clients access to file “B”. File “B” is kept in the domain of the LM 220-2. A lock request comprises the client unique ID, the client's host name, and the client process ID. The LM 220-1, upon receiving request R1, replaces the client unique ID and client's host name with a host index and a client index using the following notation host_index@domain.client_index. In addition, the LM 220-1 checks if a LR object assigned to file “B” belongs to its domain; since it does not, the LM 220-1 forwards the request R1 to the LM 220-2. The LM 220-2 saves the request R1 in its registry lock file in thedatabase 230 and detects a LR object in the MD server 250-2 assigned to file “B”. If such a LR object does not exist, the LM 220-1 allocates a new LR object. It should be noted that while modifying the registry lock file, thedatabase 230 is locked. This is performed in order to ensure data consistency. Subsequently, the LM 220-2 checks if the request R1 can be granted. If the request is granted, the file is locked and the lock request is saved in thegrant list 430 and its status is updated to a granted state. As the lock of file “B” holds exclusive rights, all subsequent lock requests on file “B” with non-exclusive lock's mode will be denied. To allow other clients access to file “B”, the client 240-1 must send a convert request to change the lock's mode on file “B” from exclusive to non-exclusive or a request to remove the lock. In another respect, if the request R1 is denied, the LM 220-2 replies to the client 240-1 with a message notifying that the lock request is denied and then the lock request in saved in theblock queue 410. - In case of a failover or shutdown of at least one processing node, all locks managed by a LM of the failed node are released and the LR objects are deleted. For that purpose, the LM 220-1, 220-2, 220-n traverses its registry lock file to detect the locked files that are to be unlocked. If a client 240-1, 240-m fails, all the locks requested by this client are unlocked.
- Referring to
FIG. 5 , anon-limiting flowchart 500 describing the method for handling a new lock request, in accordance with an exemplary embodiment of this invention, is shown. The method is executed by a LM (e.g., LM 220-1) belonging to the same domain as that of the file requested to be locked. The type of the lock request may be handled by, but is not limited to, a share lock, a byte range lock, an Oplock and other lock schemes. At S510, a new lock request received at a LM acquires a unique ID. At S520, thedatabase 230 is locked for preventing other clients to write to thedatabase 230 and the new request's parameters are saved in the in the registry lock file (e.g., registry lock file 300) corresponds to the LM that received the request. The request parameters comprise a client unique ID (or a client index), a host name (or a host index), a request unique ID, and the request creation time. Once the writing to the registry lock files is completed, thedatabase 230 is unlocked. At S530, a check is made to determine if the convert queue is empty, and if so, execution continues with S540; otherwise, the execution continues at S580 where the request is blocked. At S540; a check is performed to determine if the block queue is empty and if so the execution continues with S550; otherwise, the execution continues with S580. At S550 another check is made to determine if the request can be satisfied. Specifically, it is checked whether the lock request is in conflict with an already granted lock saved in the grant list. If the request can be satisfied, at S560, the lock's status in the registry lock file is updated to a granted state and the request is added to the grant list. At S570, a message is send to the client notifying the lock request is granted. If the lock request is denied, the execution continues with S580. - Referring to
FIG. 6 , a detailed flowchart describing the blocking of a request (S580) is shown. At S610, the request status in the registry lock file is set to a blocked mode. At S620, the request is added to the block queue. At S630, the request and its wakeup time are saved in the wakeup list. S630 is performed only if the request comprises a timeout parameter, which defines the duration time of the request. The duration time defines the amount of time that a lock request waits to a lock to be unlocked. At S640, a message is sent to the requesting client notifying that the lock request is blocked. - Referring to
FIG. 7 , anon-limiting flowchart 700 describing the method for handling a convert request, in accordance with an exemplary embodiment of this invention, is shown. The method is executed by a LM (e.g., LM 220-1) belonging to the same domain as that of the file being locked. The type of the lock request to be handled may be, but is not limited to, a share lock, a byte range lock, an Oplock and other lock schemes. A client can request to upgrade the lock's mode, i.e., to change lock's mode from a non-exclusive to exclusive mode or to downgrade the lock's mode, i.e., to change the mode from an exclusive to non-exclusive mode. At S710, a new convert request is received at a LM. The convert request comprises the client unique ID (or client index), client's host name (or host index) and the lock ID of the lock to be converted. At S720, the lock request list (e.g., list 310) in the registry lock file (e.g., registry lock file 300) of the LM receiving the request is being searched in order to identify an entry associated with the lock requested to be converted. The search is made using the lock's unique ID. At S730, a check is made to determine if a lock having the same lock ID as designated in the request is found, and if so the execution continues with S740; otherwise, the request is denied and execution ends. It should be noted that a request for converting the mode of a non-granted lock is also denied. At S740, a check is made to determine if theconvert queue 420 is empty, and if so execution continues at S760; otherwise, execution continues with S750 where the lock's mode is changed to the new requested mode. At S755, the status of the lock is set to converted state and the lock is added to theconvert queue 420. At S760, a check is made to determine if the convert lock request can be satisfied. Specifically, it is checked whether the requested mode is compatible with the most restrictive mode of the currently granted lock. If the request is satisfied, then at S770, the lock's status is set to a granted state and the lock is added to the grant list. If the request is denied, then at S780 the lock status is set to a converted state and the lock is added to theconvert queue 420. At S785, the request and its wakeup time are saved in thewakeup list 440. S785 is performed only if the request comprises a timeout parameter. At S790, a message is sent to the requesting client notifying the request is denied. - In an exemplary embodiment of the present invention, the method and the DLS disclosed herein can be operated in a mixed mode, namely to handle concurrently lock requests utilized through different file sharing protocols. Each protocol defines its own requirements to impose a lock on a file. These different requirements of the lock mode should be addressed by the
DLS 200 while operating is a mixed mode. For example, the CIFS protocol requires that file byte range locks be granted only after a share lock is granted on the file, while in the NFS protocol only byte range locks can be used. - As all NFS requests are byte range lock requests, in a mixed mode of operation a share lock entry for each client is created. Specifically, a first byte range lock request from a client creates a share lock request. If the share lock is compatible with currently granted locks this request will be satisfied. After granting a share lock on the file, the requested byte range is locked. The restrictive mode of the byte range lock is the mode of the share lock on the locked file.
- In an exemplary embodiment of the present invention, the DLS and the methods for handling the lock requests disclosed herein can be operated in conjunction with a distributed shared files system (DSFS) disclosed in U.S. patent application Ser. No. 10/265,778, entitled “Flexible and Adaptive Read and Write Storage System Architecture” assigned to common assignee and which is hereby incorporated by reference for all that it contains.
- The foregoing description of the exemplary embodiments of the invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from practice of the invention. The exemplary embodiments were chosen and described in order to explain the principles of the invention and its practical application to enable one skilled in the art to utilize the invention in various embodiments and with various modifications as are suited to the particular use contemplated.
- Thus, while only exemplary embodiments of the invention have been specifically described herein, it will be apparent that numerous modifications may be made thereto without departing from the spirit and scope of the invention. Further, acronyms are used merely to enhance the readability of the specification and claims. It should be noted that these acronyms are not intended to lessen the generality of the terms used and they should not be construed to restrict the scope of the claims to the exemplary embodiments described therein.
Claims (44)
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/159,216 US20050289143A1 (en) | 2004-06-23 | 2005-06-23 | Method for managing lock resources in a distributed storage system |
US12/333,868 US8086581B2 (en) | 2004-06-23 | 2008-12-12 | Method for managing lock resources in a distributed storage system |
US13/312,594 US8566299B2 (en) | 2004-06-23 | 2011-12-06 | Method for managing lock resources in a distributed storage system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US58172104P | 2004-06-23 | 2004-06-23 | |
US11/159,216 US20050289143A1 (en) | 2004-06-23 | 2005-06-23 | Method for managing lock resources in a distributed storage system |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/333,868 Continuation US8086581B2 (en) | 2004-06-23 | 2008-12-12 | Method for managing lock resources in a distributed storage system |
Publications (1)
Publication Number | Publication Date |
---|---|
US20050289143A1 true US20050289143A1 (en) | 2005-12-29 |
Family
ID=35507320
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/159,216 Abandoned US20050289143A1 (en) | 2004-06-23 | 2005-06-23 | Method for managing lock resources in a distributed storage system |
US12/333,868 Active 2026-08-14 US8086581B2 (en) | 2004-06-23 | 2008-12-12 | Method for managing lock resources in a distributed storage system |
US13/312,594 Active 2025-07-18 US8566299B2 (en) | 2004-06-23 | 2011-12-06 | Method for managing lock resources in a distributed storage system |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/333,868 Active 2026-08-14 US8086581B2 (en) | 2004-06-23 | 2008-12-12 | Method for managing lock resources in a distributed storage system |
US13/312,594 Active 2025-07-18 US8566299B2 (en) | 2004-06-23 | 2011-12-06 | Method for managing lock resources in a distributed storage system |
Country Status (1)
Country | Link |
---|---|
US (3) | US20050289143A1 (en) |
Cited By (57)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060136508A1 (en) * | 2004-12-16 | 2006-06-22 | Sam Idicula | Techniques for providing locks for file operations in a database management system |
US20060136509A1 (en) * | 2004-12-16 | 2006-06-22 | Syam Pannala | Techniques for transaction semantics for a database server performing file operations |
US20060136516A1 (en) * | 2004-12-16 | 2006-06-22 | Namit Jain | Techniques for maintaining consistency for different requestors of files in a database management system |
US20060136376A1 (en) * | 2004-12-16 | 2006-06-22 | Oracle International Corporation | Infrastructure for performing file operations by a database server |
US20060167878A1 (en) * | 2005-01-27 | 2006-07-27 | International Business Machines Corporation | Customer statistics based on database lock use |
US20070005555A1 (en) * | 2005-06-29 | 2007-01-04 | Namit Jain | Method and mechanism for supporting virtual content in performing file operations at a RDBMS |
US20070005603A1 (en) * | 2005-06-29 | 2007-01-04 | Namit Jain | Sharing state information among a plurality of file operation servers |
US20070007785A1 (en) * | 2005-07-08 | 2007-01-11 | Marathon Marine Manufacturing (1996) Ltd. | Cargo deck for truck box |
US20070130157A1 (en) * | 2005-12-05 | 2007-06-07 | Namit Jain | Techniques for performing file operations involving a link at a database management system |
US20070136289A1 (en) * | 2005-12-14 | 2007-06-14 | Intel Corporation | Lock elision with transactional memory |
US20070143755A1 (en) * | 2005-12-16 | 2007-06-21 | Intel Corporation | Speculative execution past a barrier |
US20070168423A1 (en) * | 2006-01-18 | 2007-07-19 | Kum-Rye Park | Video conferencing using white board |
US20070214142A1 (en) * | 2006-03-10 | 2007-09-13 | Prabhakar Goyal | System and method for providing transaction support across a plurality of data structures |
US20070214457A1 (en) * | 2006-03-10 | 2007-09-13 | Prabhakar Goyal | System and method for automated recovery of data in a batch processing system |
US20070214161A1 (en) * | 2006-03-10 | 2007-09-13 | Prabhakar Goyal | System and method for resource lock acquisition and reclamation in a network file system environment |
US20080082533A1 (en) * | 2006-09-28 | 2008-04-03 | Tak Fung Wang | Persistent locks/resources for concurrency control |
US20100023521A1 (en) * | 2008-07-28 | 2010-01-28 | International Business Machines Corporation | System and method for managing locks across distributed computing nodes |
US20100106934A1 (en) * | 2008-10-24 | 2010-04-29 | Microsoft Corporation | Partition management in a partitioned, scalable, and available structured storage |
US20100106697A1 (en) * | 2008-10-06 | 2010-04-29 | International Business Machines Corporation | System for accessing shared data using multiple application servers |
WO2010048027A3 (en) * | 2008-10-24 | 2010-06-17 | Microsoft Corporation | Atomic multiple modification of data in a distributed storage system |
US20100250507A1 (en) * | 2009-03-31 | 2010-09-30 | Microsoft Corporation | Enumeration of a concurrent data structure |
US20110246435A1 (en) * | 2010-03-31 | 2011-10-06 | Salesforce.Com, Inc. | System, method and computer program product for maintaining data stored in a data structure |
US20120078866A1 (en) * | 2004-06-23 | 2012-03-29 | Dell Global B.V. - Singapore Branch | Method For Managing Lock Resources in a Distributed Storage System |
US20120226673A1 (en) * | 2011-03-01 | 2012-09-06 | Vmware, Inc. | Configuration-less network locking infrastructure for shared file systems |
WO2013000135A1 (en) * | 2011-06-29 | 2013-01-03 | 中兴通讯股份有限公司 | Locking method and system for distributed messages |
US20130018861A1 (en) * | 2011-07-11 | 2013-01-17 | Oracle International Corporation | Dual locking mechanism for a domain |
US20140068127A1 (en) * | 2012-09-04 | 2014-03-06 | Red Hat Israel, Ltd. | Shared locking mechanism for storage centric leases |
US20140115091A1 (en) * | 2012-10-19 | 2014-04-24 | Apacer Technology Inc. | Machine-implemented file sharing method for network storage system |
CN103997498A (en) * | 2014-05-27 | 2014-08-20 | 北京京东尚科信息技术有限公司 | Distributed lock service implementation method and component |
US20140280347A1 (en) * | 2013-03-14 | 2014-09-18 | Konica Minolta Laboratory U.S.A., Inc. | Managing Digital Files with Shared Locks |
US20140321855A1 (en) * | 2011-11-08 | 2014-10-30 | Telefonaktiebolaget L M Ericsson (Publ) | Ont connected to a host device |
WO2014194678A1 (en) * | 2013-06-06 | 2014-12-11 | 华为技术有限公司 | Lock operation method of database system, and device |
US20140365597A1 (en) * | 2013-06-07 | 2014-12-11 | International Business Machines Corporation | Processing Element Data Sharing |
US20150019739A1 (en) * | 2010-10-11 | 2015-01-15 | International Business Machines Corporation | Two-level management of locks on shared resources |
US20150378771A1 (en) * | 2014-06-28 | 2015-12-31 | Vmware, Inc. | Using a delta query to seed live migration |
US9552217B2 (en) | 2014-06-28 | 2017-01-24 | Vmware, Inc. | Using active/active asynchronous replicated storage for live migration |
US9578130B1 (en) * | 2012-06-20 | 2017-02-21 | Amazon Technologies, Inc. | Asynchronous and idempotent distributed lock interfaces |
WO2017032418A1 (en) * | 2015-08-27 | 2017-03-02 | Telefonaktiebolaget Lm Ericsson (Publ) | Message processing node and database in a message processing system and methods of operating the same |
US9672120B2 (en) | 2014-06-28 | 2017-06-06 | Vmware, Inc. | Maintaining consistency using reverse replication during live migration |
US9760443B2 (en) | 2014-06-28 | 2017-09-12 | Vmware, Inc. | Using a recovery snapshot during live migration |
US9766930B2 (en) | 2014-06-28 | 2017-09-19 | Vmware, Inc. | Using active/passive asynchronous replicated storage for live migration |
CN107181789A (en) * | 2017-03-31 | 2017-09-19 | 北京奇艺世纪科技有限公司 | A kind of distributed lock implementation method and device |
US20170364545A1 (en) * | 2016-06-21 | 2017-12-21 | Unisys Corporation | Systems and methods for implementing a multi-host record lock mechanism |
US9852221B1 (en) | 2015-03-26 | 2017-12-26 | Amazon Technologies, Inc. | Distributed state manager jury selection |
CN109063132A (en) * | 2018-08-02 | 2018-12-21 | 上海达梦数据库有限公司 | Latch requesting method, latch authorization method, device and terminal device |
US10264071B2 (en) | 2014-03-31 | 2019-04-16 | Amazon Technologies, Inc. | Session management in distributed storage systems |
US10372685B2 (en) | 2014-03-31 | 2019-08-06 | Amazon Technologies, Inc. | Scalable file storage service |
US10459810B2 (en) | 2017-07-06 | 2019-10-29 | Oracle International Corporation | Technique for higher availability in a multi-node system using replicated lock information to determine a set of data blocks for recovery |
US10671545B2 (en) | 2014-06-28 | 2020-06-02 | Vmware, Inc. | Asynchronous encryption and decryption of virtual machine memory for live migration |
CN113505103A (en) * | 2021-07-27 | 2021-10-15 | 浙江大华技术股份有限公司 | File processing method and device, storage medium and electronic device |
US20220269965A1 (en) * | 2021-02-24 | 2022-08-25 | Red Hat, Inc. | Access protection for shared qubits |
US20230117060A1 (en) * | 2020-01-17 | 2023-04-20 | Inspur Suzhou Intelligent Technology Co., Ltd. | Read-write method and apparatus, electronic device, and readable memory medium |
US11636068B2 (en) * | 2019-05-09 | 2023-04-25 | Citrix Systems, Inc. | Distributed file locking for a network file share |
US20230244641A1 (en) * | 2022-01-28 | 2023-08-03 | Dell Products L.P. | Using a logical operation coalescer to concurrently update file system objects |
US11783067B2 (en) | 2020-10-13 | 2023-10-10 | Microsoft Technology Licensing, Llc | Setting modification privileges for application instances |
US20240020290A1 (en) * | 2022-07-14 | 2024-01-18 | Dell Products L.P. | System B-Tree Change Notification System Using Lock Value Blocks |
CN117519945A (en) * | 2023-12-07 | 2024-02-06 | 北京优炫软件股份有限公司 | Database resource scheduling method, device and system |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7743039B2 (en) * | 2006-12-11 | 2010-06-22 | Simdesk Technologies, Inc. | File operations with multiple level file locking techniques |
US9984097B2 (en) * | 2010-11-10 | 2018-05-29 | International Business Machines Corporation | Systems and computer program products for transferring reserves when moving virtual machines across systems |
US9710865B1 (en) | 2011-08-15 | 2017-07-18 | Amazon Technologies, Inc. | Coordinating distributed order execution |
US8626917B2 (en) | 2012-03-16 | 2014-01-07 | Sap Ag | File access using counter locking mechanism |
US9323771B2 (en) | 2013-04-24 | 2016-04-26 | Dell Products, Lp | Efficient rename in a lock-coupled traversal of B+tree |
US9400819B2 (en) | 2013-06-07 | 2016-07-26 | Dell Products, Lp | Updating object attributes in a lock-coupled namespace traversal |
US9852146B1 (en) * | 2015-03-20 | 2017-12-26 | EMC IP Holding Company LLC | Distributed metadata servers for cluster file systems using shared low latency persistent key-value metadata store |
US10719499B2 (en) * | 2016-06-06 | 2020-07-21 | INTERNATIONAL BUSINESS MACHINES CORPORATIOb | Establishing distributed consensus via alternate voting strategies in a dispersed storage network |
US11226748B2 (en) | 2016-07-05 | 2022-01-18 | Red Hat Israel, Ltd | Differentiating open and abandoned transactions in a shared storage environment |
CN112148695A (en) * | 2019-06-26 | 2020-12-29 | 华为技术有限公司 | Resource lock management method and device |
US11082494B2 (en) * | 2019-12-05 | 2021-08-03 | Western Digital Technologies, Inc. | Cross storage protocol access response for object data stores |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5828876A (en) * | 1996-07-31 | 1998-10-27 | Ncr Corporation | File system for a clustered processing system |
US6009427A (en) * | 1996-08-02 | 1999-12-28 | Hewlett Packard Company | Method and apparatus for distributed control of a database |
US6173293B1 (en) * | 1998-03-13 | 2001-01-09 | Digital Equipment Corporation | Scalable distributed file system |
US6389420B1 (en) * | 1999-09-30 | 2002-05-14 | Emc Corporation | File manager providing distributed locking and metadata management for shared data access by clients relinquishing locks after time period expiration |
US6523078B1 (en) * | 1999-11-23 | 2003-02-18 | Steeleye Technology, Inc. | Distributed locking system and method for a clustered system having a distributed system for storing cluster configuration information |
US6601070B2 (en) * | 2001-04-05 | 2003-07-29 | Hewlett-Packard Development Company, L.P. | Distribution of physical file systems |
US6651123B1 (en) * | 2000-03-30 | 2003-11-18 | International Business Machines Corporation | File system locking |
US20050155011A1 (en) * | 2004-01-12 | 2005-07-14 | Stephan Heik | Method and system for restricting access in a distributed job environment |
US7150019B1 (en) * | 1996-06-24 | 2006-12-12 | Oracle International Corporation | Using distributed information about lock conversion requests to efficiently manage lock state transitions |
Family Cites Families (40)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPS63204437A (en) * | 1987-02-13 | 1988-08-24 | インターナシヨナル・ビジネス・マシーンズ・コーポレーシヨン | Lock system for decentralized type system |
US5060144A (en) * | 1989-03-16 | 1991-10-22 | Unisys Corporation | Locking control with validity status indication for a multi-host processor system that utilizes a record lock processor and a cache memory for each host processor |
CA2011807C (en) * | 1989-03-20 | 1999-02-23 | Katsumi Hayashi | Data base processing system using multiprocessor system |
US5226159A (en) * | 1989-05-15 | 1993-07-06 | International Business Machines Corporation | File lock management in a distributed data processing system |
US5117352A (en) * | 1989-10-20 | 1992-05-26 | Digital Equipment Corporation | Mechanism for fail-over notification |
US5226143A (en) * | 1990-03-14 | 1993-07-06 | International Business Machines Corporation | Multiprocessor system includes operating system for notifying only those cache managers who are holders of shared locks on a designated page by global lock manager |
US5339427A (en) * | 1992-03-30 | 1994-08-16 | International Business Machines Corporation | Method and apparatus for distributed locking of shared data, employing a central coupling facility |
DE69322057T2 (en) * | 1992-10-24 | 1999-06-10 | Int Computers Ltd | Distributed data processing system |
US5454108A (en) * | 1994-01-26 | 1995-09-26 | International Business Machines Corporation | Distributed lock manager using a passive, state-full control-server |
US5659682A (en) * | 1994-06-16 | 1997-08-19 | International Business Machines Corporation | Scheme to determine completion of directory operations for server recovery |
US5742813A (en) * | 1994-11-10 | 1998-04-21 | Cadis, Inc. | Method and apparatus for concurrency in an object oriented database using lock inheritance based on class objects |
JP3516362B2 (en) * | 1995-03-01 | 2004-04-05 | 富士通株式会社 | Shared data processing device and shared data processing system |
US6148377A (en) * | 1996-11-22 | 2000-11-14 | Mangosoft Corporation | Shared memory computer networks |
US5966706A (en) * | 1997-02-19 | 1999-10-12 | At&T Corp | Local logging in a distributed database management computer system |
US6105085A (en) * | 1997-12-26 | 2000-08-15 | Emc Corporation | Lock mechanism for shared resources having associated data structure stored in common memory include a lock portion and a reserve portion |
JP2001523367A (en) * | 1998-01-26 | 2001-11-20 | テレノール アクティーゼルスカブ | Database management system and method for combining metadata for conditional contention serializability of transactions and varying degrees of reliability |
US6332197B1 (en) * | 1998-08-04 | 2001-12-18 | International Business Machines Corp. | System for updating data in a multi-adaptor environment |
US6189007B1 (en) * | 1998-08-28 | 2001-02-13 | International Business Machines Corporation | Method and apparatus for conducting a high performance locking facility in a loosely coupled environment |
US6148414A (en) * | 1998-09-24 | 2000-11-14 | Seek Systems, Inc. | Methods and systems for implementing shared disk array management functions |
GB2342198B (en) * | 1998-10-02 | 2003-10-22 | Ibm | Composite locking of objects in a database |
US6438548B1 (en) * | 1999-06-30 | 2002-08-20 | International Business Machines Corporation | Method of and system for managing documents in a bandwidth constrained environment |
US6965893B1 (en) * | 2000-12-20 | 2005-11-15 | Oracle International Corporation | Techniques for granting shared locks more efficiently |
US6842809B2 (en) * | 2001-04-12 | 2005-01-11 | International Business Machines Corporation | Apparatus, method and computer program product for converting simple locks in a multiprocessor system |
US7743109B2 (en) * | 2001-08-01 | 2010-06-22 | Cisco Technology, Inc. | Reducing round trips across a wide area network for resource locking by extended locking and delayed unlocking |
US6748470B2 (en) * | 2001-11-13 | 2004-06-08 | Microsoft Corporation | Method and system for locking multiple resources in a distributed environment |
US7146366B2 (en) * | 2002-09-13 | 2006-12-05 | Netezza Corporation | Distributed concurrency control using serialization ordering |
US7337290B2 (en) * | 2003-04-03 | 2008-02-26 | Oracle International Corporation | Deadlock resolution through lock requeing |
US7233946B1 (en) * | 2003-04-11 | 2007-06-19 | Sun Microsystems, Inc. | File interval lock generation interface system and method |
US7340743B1 (en) * | 2003-04-25 | 2008-03-04 | Symantec Operating Corporation | Masterless locks in a multi-node environment |
US7124131B2 (en) * | 2003-04-29 | 2006-10-17 | International Business Machines Corporation | Discipline for lock reassertion in a distributed file system |
US7779039B2 (en) * | 2004-04-02 | 2010-08-17 | Salesforce.Com, Inc. | Custom entities and fields in a multi-tenant database system |
US7558794B2 (en) * | 2004-03-24 | 2009-07-07 | Sap Ag | Database system and method with assigned locks |
US20050289143A1 (en) * | 2004-06-23 | 2005-12-29 | Exanet Ltd. | Method for managing lock resources in a distributed storage system |
US20060136508A1 (en) * | 2004-12-16 | 2006-06-22 | Sam Idicula | Techniques for providing locks for file operations in a database management system |
US7735089B2 (en) * | 2005-03-08 | 2010-06-08 | Oracle International Corporation | Method and system for deadlock detection in a distributed environment |
JP2007047863A (en) * | 2005-08-05 | 2007-02-22 | Hitachi Ltd | Storage system and storage control method for performing access exclusive control for every storage area unit constituting storage area of memory |
US8429753B2 (en) * | 2008-05-08 | 2013-04-23 | Microsoft Corporation | Controlling access to documents using file locks |
US8381308B2 (en) * | 2009-05-27 | 2013-02-19 | International Business Corporation | Computer-implemented multi-resource shared lock |
US8392388B2 (en) * | 2010-09-08 | 2013-03-05 | Sybase, Inc. | Adaptive locking of retained resources in a distributed database processing environment |
US9507816B2 (en) * | 2011-05-24 | 2016-11-29 | Nintendo Co., Ltd. | Partitioned database model to increase the scalability of an information system |
-
2005
- 2005-06-23 US US11/159,216 patent/US20050289143A1/en not_active Abandoned
-
2008
- 2008-12-12 US US12/333,868 patent/US8086581B2/en active Active
-
2011
- 2011-12-06 US US13/312,594 patent/US8566299B2/en active Active
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7150019B1 (en) * | 1996-06-24 | 2006-12-12 | Oracle International Corporation | Using distributed information about lock conversion requests to efficiently manage lock state transitions |
US5828876A (en) * | 1996-07-31 | 1998-10-27 | Ncr Corporation | File system for a clustered processing system |
US6009427A (en) * | 1996-08-02 | 1999-12-28 | Hewlett Packard Company | Method and apparatus for distributed control of a database |
US6173293B1 (en) * | 1998-03-13 | 2001-01-09 | Digital Equipment Corporation | Scalable distributed file system |
US6389420B1 (en) * | 1999-09-30 | 2002-05-14 | Emc Corporation | File manager providing distributed locking and metadata management for shared data access by clients relinquishing locks after time period expiration |
US6523078B1 (en) * | 1999-11-23 | 2003-02-18 | Steeleye Technology, Inc. | Distributed locking system and method for a clustered system having a distributed system for storing cluster configuration information |
US6651123B1 (en) * | 2000-03-30 | 2003-11-18 | International Business Machines Corporation | File system locking |
US6601070B2 (en) * | 2001-04-05 | 2003-07-29 | Hewlett-Packard Development Company, L.P. | Distribution of physical file systems |
US20050155011A1 (en) * | 2004-01-12 | 2005-07-14 | Stephan Heik | Method and system for restricting access in a distributed job environment |
Cited By (99)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120078866A1 (en) * | 2004-06-23 | 2012-03-29 | Dell Global B.V. - Singapore Branch | Method For Managing Lock Resources in a Distributed Storage System |
US8566299B2 (en) * | 2004-06-23 | 2013-10-22 | Dell Global B.V.-Singapore Branch | Method for managing lock resources in a distributed storage system |
US20060136509A1 (en) * | 2004-12-16 | 2006-06-22 | Syam Pannala | Techniques for transaction semantics for a database server performing file operations |
US20060136516A1 (en) * | 2004-12-16 | 2006-06-22 | Namit Jain | Techniques for maintaining consistency for different requestors of files in a database management system |
US20060136376A1 (en) * | 2004-12-16 | 2006-06-22 | Oracle International Corporation | Infrastructure for performing file operations by a database server |
US7548918B2 (en) * | 2004-12-16 | 2009-06-16 | Oracle International Corporation | Techniques for maintaining consistency for different requestors of files in a database management system |
US7627574B2 (en) | 2004-12-16 | 2009-12-01 | Oracle International Corporation | Infrastructure for performing file operations by a database server |
US7716260B2 (en) | 2004-12-16 | 2010-05-11 | Oracle International Corporation | Techniques for transaction semantics for a database server performing file operations |
US20060136508A1 (en) * | 2004-12-16 | 2006-06-22 | Sam Idicula | Techniques for providing locks for file operations in a database management system |
US8386449B2 (en) * | 2005-01-27 | 2013-02-26 | International Business Machines Corporation | Customer statistics based on database lock use |
US20060167878A1 (en) * | 2005-01-27 | 2006-07-27 | International Business Machines Corporation | Customer statistics based on database lock use |
US8224837B2 (en) | 2005-06-29 | 2012-07-17 | Oracle International Corporation | Method and mechanism for supporting virtual content in performing file operations at a RDBMS |
US7409397B2 (en) | 2005-06-29 | 2008-08-05 | Oracle International Corporation | Supporting replication among a plurality of file operation servers |
US7809675B2 (en) | 2005-06-29 | 2010-10-05 | Oracle International Corporation | Sharing state information among a plurality of file operation servers |
US20070005604A1 (en) * | 2005-06-29 | 2007-01-04 | Namit Jain | Supporting replication among a plurality of file operation servers |
US20070005603A1 (en) * | 2005-06-29 | 2007-01-04 | Namit Jain | Sharing state information among a plurality of file operation servers |
US20070005555A1 (en) * | 2005-06-29 | 2007-01-04 | Namit Jain | Method and mechanism for supporting virtual content in performing file operations at a RDBMS |
US20070007785A1 (en) * | 2005-07-08 | 2007-01-11 | Marathon Marine Manufacturing (1996) Ltd. | Cargo deck for truck box |
US7610304B2 (en) | 2005-12-05 | 2009-10-27 | Oracle International Corporation | Techniques for performing file operations involving a link at a database management system |
US20070130157A1 (en) * | 2005-12-05 | 2007-06-07 | Namit Jain | Techniques for performing file operations involving a link at a database management system |
US20070136289A1 (en) * | 2005-12-14 | 2007-06-14 | Intel Corporation | Lock elision with transactional memory |
US20070143755A1 (en) * | 2005-12-16 | 2007-06-21 | Intel Corporation | Speculative execution past a barrier |
US8635274B2 (en) * | 2006-01-18 | 2014-01-21 | Samsung Electronics Co., Ltd. | Video conferencing using white board |
US20070168423A1 (en) * | 2006-01-18 | 2007-07-19 | Kum-Rye Park | Video conferencing using white board |
US20070214457A1 (en) * | 2006-03-10 | 2007-09-13 | Prabhakar Goyal | System and method for automated recovery of data in a batch processing system |
US20070214142A1 (en) * | 2006-03-10 | 2007-09-13 | Prabhakar Goyal | System and method for providing transaction support across a plurality of data structures |
US7904435B2 (en) * | 2006-03-10 | 2011-03-08 | Yahoo! Inc. | System and method for resource lock acquisition and reclamation in a network file system environment |
US20070214161A1 (en) * | 2006-03-10 | 2007-09-13 | Prabhakar Goyal | System and method for resource lock acquisition and reclamation in a network file system environment |
US20080082533A1 (en) * | 2006-09-28 | 2008-04-03 | Tak Fung Wang | Persistent locks/resources for concurrency control |
US20100023521A1 (en) * | 2008-07-28 | 2010-01-28 | International Business Machines Corporation | System and method for managing locks across distributed computing nodes |
US8271437B2 (en) * | 2008-07-28 | 2012-09-18 | International Business Machines Corporation | Managing locks across distributed computing nodes |
US20100106697A1 (en) * | 2008-10-06 | 2010-04-29 | International Business Machines Corporation | System for accessing shared data using multiple application servers |
US8589438B2 (en) | 2008-10-06 | 2013-11-19 | International Business Machines Corporation | System for accessing shared data using multiple application servers |
US9031923B2 (en) | 2008-10-06 | 2015-05-12 | International Business Machines Corporation | System for accessing shared data using multiple application servers |
CN102197365A (en) * | 2008-10-24 | 2011-09-21 | 微软公司 | Atomic multiple modification of data in a distributed storage system |
WO2010048027A3 (en) * | 2008-10-24 | 2010-06-17 | Microsoft Corporation | Atomic multiple modification of data in a distributed storage system |
US9996572B2 (en) | 2008-10-24 | 2018-06-12 | Microsoft Technology Licensing, Llc | Partition management in a partitioned, scalable, and available structured storage |
US20100106934A1 (en) * | 2008-10-24 | 2010-04-29 | Microsoft Corporation | Partition management in a partitioned, scalable, and available structured storage |
US8255373B2 (en) | 2008-10-24 | 2012-08-28 | Microsoft Corporation | Atomic multiple modification of data in a distributed storage system |
US20100250507A1 (en) * | 2009-03-31 | 2010-09-30 | Microsoft Corporation | Enumeration of a concurrent data structure |
US9418175B2 (en) * | 2009-03-31 | 2016-08-16 | Microsoft Technology Licensing, Llc | Enumeration of a concurrent data structure |
US9767136B2 (en) * | 2010-03-31 | 2017-09-19 | Salesforce.Com, Inc. | System, method and computer program product for maintaining data stored in a data structure |
US11609896B2 (en) | 2010-03-31 | 2023-03-21 | Salesforce.Com, Inc. | System, method and computer program product for maintaining data stored in a data structure |
US20110246435A1 (en) * | 2010-03-31 | 2011-10-06 | Salesforce.Com, Inc. | System, method and computer program product for maintaining data stored in a data structure |
US11120003B2 (en) | 2010-03-31 | 2021-09-14 | Salesforce.Com, Inc. | System, method and computer program product for maintaining data stored in a data structure |
US20150019739A1 (en) * | 2010-10-11 | 2015-01-15 | International Business Machines Corporation | Two-level management of locks on shared resources |
US9940346B2 (en) * | 2010-10-11 | 2018-04-10 | International Business Machines Corporation | Two-level management of locks on shared resources |
US20120226673A1 (en) * | 2011-03-01 | 2012-09-06 | Vmware, Inc. | Configuration-less network locking infrastructure for shared file systems |
US9026510B2 (en) * | 2011-03-01 | 2015-05-05 | Vmware, Inc. | Configuration-less network locking infrastructure for shared file systems |
WO2013000135A1 (en) * | 2011-06-29 | 2013-01-03 | 中兴通讯股份有限公司 | Locking method and system for distributed messages |
US20130018861A1 (en) * | 2011-07-11 | 2013-01-17 | Oracle International Corporation | Dual locking mechanism for a domain |
US9218386B2 (en) * | 2011-07-11 | 2015-12-22 | Oracle International Corporation | Dual locking mechanism for a domain |
US20140321855A1 (en) * | 2011-11-08 | 2014-10-30 | Telefonaktiebolaget L M Ericsson (Publ) | Ont connected to a host device |
US9237388B2 (en) * | 2011-11-08 | 2016-01-12 | Telefonaktiebolaget Lm Ericsson | ONT connected to a host device |
US10116766B2 (en) | 2012-06-20 | 2018-10-30 | Amazon Technologies, Inc. | Asynchronous and idempotent distributed lock interfaces |
US9578130B1 (en) * | 2012-06-20 | 2017-02-21 | Amazon Technologies, Inc. | Asynchronous and idempotent distributed lock interfaces |
US20140068127A1 (en) * | 2012-09-04 | 2014-03-06 | Red Hat Israel, Ltd. | Shared locking mechanism for storage centric leases |
US9542237B2 (en) * | 2012-09-04 | 2017-01-10 | Red Hat Israel, Ltd. | Shared locking for storage centric exclusive locks |
US20140115091A1 (en) * | 2012-10-19 | 2014-04-24 | Apacer Technology Inc. | Machine-implemented file sharing method for network storage system |
US20140280347A1 (en) * | 2013-03-14 | 2014-09-18 | Konica Minolta Laboratory U.S.A., Inc. | Managing Digital Files with Shared Locks |
WO2014194678A1 (en) * | 2013-06-06 | 2014-12-11 | 华为技术有限公司 | Lock operation method of database system, and device |
US9449041B2 (en) | 2013-06-06 | 2016-09-20 | Huawei Technologies Co., Ltd. | Database system lock operation method and device |
US9317472B2 (en) * | 2013-06-07 | 2016-04-19 | International Business Machines Corporation | Processing element data sharing |
US20160179709A1 (en) * | 2013-06-07 | 2016-06-23 | International Business Machines Corporation | Processing element data sharing |
US20140365597A1 (en) * | 2013-06-07 | 2014-12-11 | International Business Machines Corporation | Processing Element Data Sharing |
US9569378B2 (en) * | 2013-06-07 | 2017-02-14 | International Business Machines Corporation | Processing element data sharing |
US10372685B2 (en) | 2014-03-31 | 2019-08-06 | Amazon Technologies, Inc. | Scalable file storage service |
US10264071B2 (en) | 2014-03-31 | 2019-04-16 | Amazon Technologies, Inc. | Session management in distributed storage systems |
CN103997498A (en) * | 2014-05-27 | 2014-08-20 | 北京京东尚科信息技术有限公司 | Distributed lock service implementation method and component |
US9760443B2 (en) | 2014-06-28 | 2017-09-12 | Vmware, Inc. | Using a recovery snapshot during live migration |
US9588796B2 (en) | 2014-06-28 | 2017-03-07 | Vmware, Inc. | Live migration with pre-opened shared disks |
US10671545B2 (en) | 2014-06-28 | 2020-06-02 | Vmware, Inc. | Asynchronous encryption and decryption of virtual machine memory for live migration |
US10579409B2 (en) | 2014-06-28 | 2020-03-03 | Vmware, Inc. | Live migration of virtual machines with memory state sharing |
US9898320B2 (en) * | 2014-06-28 | 2018-02-20 | Vmware, Inc. | Using a delta query to seed live migration |
US9672120B2 (en) | 2014-06-28 | 2017-06-06 | Vmware, Inc. | Maintaining consistency using reverse replication during live migration |
US9626212B2 (en) | 2014-06-28 | 2017-04-18 | Vmware, Inc. | Live migration of virtual machines with memory state sharing |
US20150378771A1 (en) * | 2014-06-28 | 2015-12-31 | Vmware, Inc. | Using a delta query to seed live migration |
US9552217B2 (en) | 2014-06-28 | 2017-01-24 | Vmware, Inc. | Using active/active asynchronous replicated storage for live migration |
US9766930B2 (en) | 2014-06-28 | 2017-09-19 | Vmware, Inc. | Using active/passive asynchronous replicated storage for live migration |
US10394668B2 (en) | 2014-06-28 | 2019-08-27 | Vmware, Inc. | Maintaining consistency using reverse replication during live migration |
US10394656B2 (en) | 2014-06-28 | 2019-08-27 | Vmware, Inc. | Using a recovery snapshot during live migration |
US9852221B1 (en) | 2015-03-26 | 2017-12-26 | Amazon Technologies, Inc. | Distributed state manager jury selection |
WO2017032418A1 (en) * | 2015-08-27 | 2017-03-02 | Telefonaktiebolaget Lm Ericsson (Publ) | Message processing node and database in a message processing system and methods of operating the same |
US11620273B2 (en) * | 2015-08-27 | 2023-04-04 | Telefonaktiebolaget Lm Ericsson (Publ) | Message processing node and database in a message processing system and methods of operating the same |
US10423603B2 (en) * | 2016-06-21 | 2019-09-24 | Unisys Corporation | Systems and methods for implementing a multi-host record lock mechanism |
US20170364545A1 (en) * | 2016-06-21 | 2017-12-21 | Unisys Corporation | Systems and methods for implementing a multi-host record lock mechanism |
CN107181789A (en) * | 2017-03-31 | 2017-09-19 | 北京奇艺世纪科技有限公司 | A kind of distributed lock implementation method and device |
US10459810B2 (en) | 2017-07-06 | 2019-10-29 | Oracle International Corporation | Technique for higher availability in a multi-node system using replicated lock information to determine a set of data blocks for recovery |
CN109063132A (en) * | 2018-08-02 | 2018-12-21 | 上海达梦数据库有限公司 | Latch requesting method, latch authorization method, device and terminal device |
US11636068B2 (en) * | 2019-05-09 | 2023-04-25 | Citrix Systems, Inc. | Distributed file locking for a network file share |
US20230117060A1 (en) * | 2020-01-17 | 2023-04-20 | Inspur Suzhou Intelligent Technology Co., Ltd. | Read-write method and apparatus, electronic device, and readable memory medium |
US11868620B2 (en) * | 2020-01-17 | 2024-01-09 | Inspur Suzhou Intelligent Technology Co., Ltd. | Read-write method and apparatus, electronic device, and readable memory medium |
US11783067B2 (en) | 2020-10-13 | 2023-10-10 | Microsoft Technology Licensing, Llc | Setting modification privileges for application instances |
US20220269965A1 (en) * | 2021-02-24 | 2022-08-25 | Red Hat, Inc. | Access protection for shared qubits |
CN113505103A (en) * | 2021-07-27 | 2021-10-15 | 浙江大华技术股份有限公司 | File processing method and device, storage medium and electronic device |
US20230244641A1 (en) * | 2022-01-28 | 2023-08-03 | Dell Products L.P. | Using a logical operation coalescer to concurrently update file system objects |
US11921678B2 (en) * | 2022-01-28 | 2024-03-05 | Dell Products L.P. | Using a logical operation coalescer to concurrently update file system objects |
US20240020290A1 (en) * | 2022-07-14 | 2024-01-18 | Dell Products L.P. | System B-Tree Change Notification System Using Lock Value Blocks |
CN117519945A (en) * | 2023-12-07 | 2024-02-06 | 北京优炫软件股份有限公司 | Database resource scheduling method, device and system |
Also Published As
Publication number | Publication date |
---|---|
US20120078866A1 (en) | 2012-03-29 |
US8086581B2 (en) | 2011-12-27 |
US8566299B2 (en) | 2013-10-22 |
US20090094243A1 (en) | 2009-04-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8566299B2 (en) | Method for managing lock resources in a distributed storage system | |
US6205466B1 (en) | Infrastructure for an open digital services marketplace | |
US7409397B2 (en) | Supporting replication among a plurality of file operation servers | |
US8296340B2 (en) | Managing files using layout storage objects | |
US8977659B2 (en) | Distributing files across multiple, permissibly heterogeneous, storage devices | |
US6973455B1 (en) | File server system providing direct data sharing between clients with a server acting as an arbiter and coordinator | |
US6453354B1 (en) | File server system using connection-oriented protocol and sharing data sets among data movers | |
US6339793B1 (en) | Read/write data sharing of DASD data, including byte file system data, in a cluster of multiple data processing systems | |
US6324581B1 (en) | File server system using file system storage, data movers, and an exchange of meta data among data movers for file locking and direct access to shared file systems | |
US7120631B1 (en) | File server system providing direct data sharing between clients with a server acting as an arbiter and coordinator | |
US7392261B2 (en) | Method, system, and program for maintaining a namespace of filesets accessible to clients over a network | |
US7194467B2 (en) | Using whole-file and dual-mode locks to reduce locking traffic in data storage systems | |
KR100825721B1 (en) | System and method of time-based cache coherency maintenance in user file manager of object-based storage system | |
US20070011136A1 (en) | Employing an identifier for an account of one domain in another domain to facilitate access of data on shared storage media | |
US20090112921A1 (en) | Managing files using layout storage objects | |
US20090112789A1 (en) | Policy based file management | |
US20030172146A1 (en) | Aggregation of available storage capacity derived from storage devices attached to computers, and allocation of same as logical device | |
US9122397B2 (en) | Exposing storage resources with differing capabilities | |
US20030191745A1 (en) | Delegation of metadata management in a storage system by leasing of free file system blocks and i-nodes from a file system owner | |
KR20040107412A (en) | Mechanism for exposing shadow copies in a networked environment | |
WO2012083797A1 (en) | Write lock method and system for distributed file system | |
US6611848B1 (en) | Methods for maintaining data and attribute coherency in instances of sharable files | |
US6687716B1 (en) | File consistency protocols and methods for carrying out the protocols | |
US20070005555A1 (en) | Method and mechanism for supporting virtual content in performing file operations at a RDBMS | |
US6633870B1 (en) | Protocols for locking sharable files and methods for carrying out the protocols |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: EXANET LTD., ISRAEL Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:OSHRI, OFER;DANIELI, NADAV;HAMBURGER, MENNY;REEL/FRAME:016720/0814;SIGNING DATES FROM 20050619 TO 20050622 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: DELL GLOBAL B.V. - SINGAPORE BRANCH,SINGAPORE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HAVER, TEMPORARY LIQUIDATOR, EREZ;REEL/FRAME:023950/0606 Effective date: 20100218 Owner name: DELL GLOBAL B.V. - SINGAPORE BRANCH, SINGAPORE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HAVER, TEMPORARY LIQUIDATOR, EREZ;REEL/FRAME:023950/0606 Effective date: 20100218 |