[go: up one dir, main page]

WO2012083797A1 - Procédé et système de verrouillage en écriture pour un système de fichiers distribué - Google Patents

Procédé et système de verrouillage en écriture pour un système de fichiers distribué Download PDF

Info

Publication number
WO2012083797A1
WO2012083797A1 PCT/CN2011/083694 CN2011083694W WO2012083797A1 WO 2012083797 A1 WO2012083797 A1 WO 2012083797A1 CN 2011083694 W CN2011083694 W CN 2011083694W WO 2012083797 A1 WO2012083797 A1 WO 2012083797A1
Authority
WO
WIPO (PCT)
Prior art keywords
file
lock
specific data
data block
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.)
Ceased
Application number
PCT/CN2011/083694
Other languages
English (en)
Chinese (zh)
Inventor
朱鹏
江凌生
王瑜
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Publication of WO2012083797A1 publication Critical patent/WO2012083797A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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

Definitions

  • the present invention relates to the field of data storage, and in particular to a write locking method and system for a distributed file system. Background technique
  • a unified locking node is usually selected to centrally lock and manage the data stored in the distributed file system.
  • the locking node can be a single server or cluster.
  • the locking node (locking server or cluster) is simply referred to as a locking server.
  • Cloud storage refers to a system that integrates a large number of different types of storage devices on a network through application software through cluster applications or distributed file systems to provide data storage and service access functions.
  • Cloud storage is a cloud computing system with data storage and management at its core. In cloud storage, both security and cost are considered, so how to deploy the cloud is key. Especially nowadays, the scale of the cloud is getting bigger and bigger, more and more clouds will be distributed in multiple places, and how to deploy the distributed file system locking server will become very complicated.
  • the present invention is directed to the deficiencies of the prior art, and provides a write locking method and system for a distributed file system, which not only ensures that the throughput of the distributed file system lock submission is improved without increasing the hardware investment, but also can With the expansion of the distributed file system and simultaneous expansion, it has good scalability.
  • the present invention provides the following technical solutions:
  • a write locking method for a distributed file system includes the following steps:
  • the upper layer data location registration server When the upper layer data location registration server receives the request for writing the open file sent by the file requesting client, the upper layer data location registration server extracts the data block path information of the file, and returns the file request client to the file;
  • the lower layer locking server returns, according to the file request, a lock request of the specific data part of the specific data block of the specific data block according to the data block path information, and the write lock permission information of the specific data part of the specific data block is returned. Request the client for the file.
  • the method further includes:
  • the upper layer data location registration server When the upper layer data location registration server extracts the data block path information of the file and finds that there is no data block path information of the file, the upper layer data location registration server creates a unique complete data block path for the file, and records Data block path information of the file, and distributes write lock rights of different data blocks on the data block path of the file to the lower layer lock server.
  • the method further includes: The file requesting client sends a lock request to the lower layer lock server for a specific data portion of the specific data block;
  • the method further includes:
  • the file requesting client determines a lock condition of the specific data portion in its own local cache, and when the specific data portion is already in its own local cache and has been locked, the file request client does not
  • the lower layer lock server sends a lock request; when the specific data portion is not locked, the file request client sends a lock request to the lower layer lock server.
  • the method before the file requesting, by the lower layer locking server, the lock request of the specific data part of the specific data block sent by the client, the method further includes: creating a data by the lower layer locking server Block lock status information table;
  • the lower lock server creates a data block lock status information table as:
  • the lower layer locking server When the lower layer locking server receives the lock request sent by the file requesting client to the specific data portion of the specific data block, the lower layer locking server determines whether it is currently receiving the specific data for the first time. Block lock request, when it is the first time, adding the specific data block and its corresponding lock request information to the data block lock status information table; when not for the first time, locking the data block The lock information of the specific data portion of the specific data block is retrieved in the status information table.
  • the method further includes:
  • the determining whether to notify the lower layer data block server to send the specific data portion required by the file requesting client to the file request client is:
  • the lower layer locking server After the lower layer locking server receives the read/write lock request sent by the file requesting client to the specific data portion of the specific data block, the lower layer locking server checks the specific content in the current data block lock status information table. a locking condition of the data portion, when the specific data portion is not locked, marking the locking state of the specific data portion as locking in the data block locking state information table, and notifying the lower layer data block server to return the specific The data portion requests the client for the file; when the specific data portion has been locked, performing a lock failure policy;
  • the lower layer lock server After the lower layer lock server receives the write lock request sent by the file request client for the specific data portion of the specific data block, the lower layer lock server checks the lock status of the current specific data portion, when The specific data portion is not locked, the lock status of the specific data portion is marked as locked in the data block status information table, and the lock is successfully returned; when the specific data portion has been locked, the lock is performed Failure strategy.
  • the file requesting client sends a read/write lock request or a write lock request to the lower layer lock server for the specific data portion of the specific data block as: the file request client check a hit situation in the local cache of the specific data portion, when the specific data portion is not in the local cache, determining that the specific data portion is not hit, and sending a read/write lock request to the lower layer lock server; When the specific data block is in the local cache and is not locked, it is determined that the specific data portion is hit, and a write lock request is sent to the lower layer lock server.
  • the present invention also provides a write lock system for a distributed file system, including a file request client, a lower layer data storage module, and an upper layer data location registration selection path module and a lower layer data locking module disposed in the system;
  • the upper layer data location registration selection path module is configured to receive a request for writing an open file sent by the file request client, and extract the data block path information of the file and return the file request request to the client;
  • the lower layer data locking module is configured to: according to the file requesting a lock request sent by a client to a specific data portion of a specific data block in the file, returning, to the write permission authority information of the specific data portion of the specific data block The file requests the client.
  • the upper layer data location registration selection path module is further configured to: when extracting data block path information of the file and discovering that there is no data block path information of the file, Creating a unique complete data block path, recording data block path information of the file, and distributing write lock rights of different data blocks on the data block path of the file to the lower data lock module.
  • the file requesting client is configured to determine that the specific data part is in itself before sending a lock request to the lower layer data locking module for the specific data part of the specific data block.
  • a lock condition in the local cache when the specific data portion is already in its own local cache and has been locked, then no lock request is sent to the underlying data lock module; when the specific data portion is not locked, A lock request is sent to the underlying data locking module.
  • the lower layer data locking module is specifically configured to: according to the file request client, a lock request for a specific data portion of the specific data block, to create the data block lock status.
  • the information table when receiving the file requesting the client to send a lock request for the specific data portion of the specific data block, determining whether it is currently receiving the lock request for the specific data block for the first time, when The first time, the specific data block and its corresponding lock request information are added in the data block lock status information table; when not the first time, the data block lock status information table is retrieved Lock request information for a specific data portion.
  • the lower layer data locking module is further configured to receive according to And the file requesting the client's lock request and the write lock permission information of the specific data portion of the specific data block returned to the file request client, determining whether to notify the lower layer data storage module to request the client from the file The specific data portion required is sent to the file request client;
  • the lower layer data locking module is configured to: after receiving the read/write lock request for the specific data portion of the specific data block sent by the file requesting client, check the specific content in the current data block locking state information table. a locking condition of the data portion, when the specific data portion is not locked, marking the locking state of the specific data portion as locking in the data block locking state information table, and notifying the lower layer data storage module to return the
  • the specific data portion requests the client for the file; when the specific data portion has been locked, executing a lock failure policy; when receiving the file requesting the client to send the specific data portion of the specific data block
  • After the write lock request checking a lock condition of the specific data portion in the current data block lock status information table, and if the specific data portion is not locked, the specific content is included in the data block status information table
  • the lock status of the data portion is marked as locked, and the lock is returned successfully; when the specific data block has been Set, perform the lock failed strategy.
  • the file requesting client is specifically configured to check a hit situation of the specific data part in a local cache, and when there is no specific data part in the local cache, determining that there is no Hiting the specific data portion, and sending a read/write lock request to the lower data lock module; when the specific data portion is in the local cache and is not locked, determining to hit the specific data portion, and The lower data locking module sends a write lock request.
  • the present invention has the beneficial effects of: determining, by the upper layer data location registration server, a unique data block path in one or more files requested by the client for the file, thereby data of the file
  • the write lock permission of different data blocks on the block path is distributed to the lower lock server, and the data block path information of the file is returned to the a file requesting client; the file requesting client initiates, according to the data block path information obtained from the upper data location registration server, a request message for writing a specific data portion of a specific data block in the file to be written to the lower layer locking server, And obtaining write lock permission information of the specific data block from the corresponding lower layer lock server.
  • the upper data storage location storage server distributes the write lock permission of all the data blocks of the file to one or more lower-level locking servers in the lower layer, and discards the traditional lock of the distributed file system by using a single locking server.
  • the method reduces the load of the locking server of the upper layer data location registration server; on the other hand, it also realizes the write lock permission of the data stored in the corresponding lower layer data block server in the lower layer locking server management distributed system, so that Increase the throughput of distributed file system lock submissions when adding distributed file system hardware resources.
  • the locking method provided by the present invention can be used in a distributed file system of one or more upper layer data location registration servers, and therefore, the locking method can improve the system throughput capability along with the distributed file system. Capacity expansion and simultaneous expansion, with good scalability.
  • FIG. 1 is a diagram showing the working architecture of an embodiment of the present invention
  • the present invention provides a write lock method and system for a distributed file system, the main idea of which is: in a distributed file system
  • the lower layer uses multiple decentralized locking servers to collectively lock data stored in the distributed file system.
  • the present invention distributes the lock permission of the data stored in the distributed file system to be locked to a plurality of different file system data servers in the lower layer.
  • the file system data server mainly includes The lower layer locking server and the lower layer data block server, wherein the lower layer data block server is mainly used to store the data block information in the distributed file system, and the lower layer locking server is mainly used to lock the data stored in the lower layer data block server, that is, The lock permission of the data in the data block server is managed.
  • the lock permission mentioned here mainly refers to the write lock permission of data in the distributed file system.
  • the write locking method determines a unique complete data block path through a file of one or more files requested by the upper layer data location registration server for the file request client to open, so that different data blocks on the data block path of the file
  • the write lock permissions are distributed to multiple lower-level locking servers.
  • the data block path information stored in the lower layer data block server is also referred to as metadata.
  • a dedicated locking server is used to lock the metadata.
  • a plurality of distributed lower-level locking servers are used to lock the data blocks stored in the lower-level data block server.
  • the write locking method provided by the present invention uses a plurality of distributed lower-level locking servers to lock data in the distributed file system, mainly to reduce the load of the locking server of the upper-layer data location registration server.
  • the upper layer data location registration server distributes the write lock permission of different data blocks in the file requested by the client requesting client to the lower lock server, so that the lower file system data server is no longer a buffer of the upper lock server. Realize the write lock permission of the underlying lock server to manage data in the distributed file system.
  • the write lock method can be widely used in a single or multiple upper layer data location registration server. If used in a plurality of upper layer data location registration servers, each upper layer data location registration server does not have a primary standby relationship.
  • the upper layer data location registration server when the upper layer data location registration server extracts a certain When the data block path information of the specific file is found and the data block path information of the file is not found, for example, the data block path information of the file A is not found, it indicates that the upper layer data location registration server is the first time to receive the file request client.
  • the write open request for the specific file A is sent, then the upper data location registration server first creates a unique complete data block path for the specific file A, and records the data block path information of the file A.
  • the write lock permission of different data blocks on the data block path of file A is distributed to the lower layer lock server, thereby achieving the finest granularity (byte level) of locking.
  • the data block path can describe path information of all data blocks in the file A, and mainly includes which data blocks are located in the file data block path and in which lower layer data block server the data blocks are stored. It should be noted that at this time, the lower-level locking server does not know that it manages the write lock permission of these data blocks.
  • the upper layer data location registration server can extract the file A.
  • the block path information is returned to the file request client.
  • the file requesting client that sends the write open file A request for the first time and the file request client that sends the write open file A request for the second time can request the client for the same file, or can request for different files.
  • Client At the same time, when the two files request the client to write and lock the same data block in the file A, they will access the same underlying data block server that stores the data block.
  • the file requesting client determines, before the lower layer locking server sends a lock request for the specific data portion of the specific data block in the file A, the specific data portion is in the file request client local cache. Lock the situation.
  • a specific data block is simply referred to as a data block B.
  • the file request client does not need to send a lock request to the lower layer lock server, and can directly start writing the data block B specific Operation of the data part; if the specific data part of the data block B is not locked, there may be two cases at this time, one is The file request does not have a specific data portion of the data block B in the local cache of the client, and in another case, there is a specific data portion of the data block B in the local cache of the file requesting client, but the specific data portion is not locked, for this In either case, the file requests the client to send a lock request to the lower level lock server.
  • the lower layer locking server creates a data block lock state information table according to a lock request sent by the client to the specific data portion of the specific data block, in a specific manner: when the lower layer locks the server C Upon receiving the file requesting client to send a lock request for the specific data portion of the data block B, the lower layer locking server C needs to determine whether it is currently the first time the file request client receives the lock on the data block B. The request, if it is, the lower level lock server C knows that it manages the write lock permission of the data block B. It also indicates that there is no information about the data block B in the existing data block lock status information table stored in the lower layer lock server C.
  • the lower layer locking server C adds the entry of the data block B and the corresponding lock request information of the data block B in the data block lock state information table; if not, the lower layer lock server C only needs to lock the state information in the current data block.
  • the table can retrieve the lock request information of the specific data portion of the data block B.
  • the lower-layer locking server C does not receive the lock request for the specific data portion of the data block B sent by the file requesting client for the first time, that is, at this time, the lower-layer locking server C Retrieving the relevant write lock permission of the specific data portion of the data block B according to the received file requesting the different lock request of the client, and returning the write lock permission information of the specific data portion of the client data block B to the file request, and determining whether to notify the lower layer
  • the lower data block server corresponding to the lock server C sends the specific data portion required by the file request client to the file request client, specifically: when the lower layer lock server receives the file request client and sends the data block B specific When the data portion D is read or written by the lock request, the specific data portion D is the offset of the file A for the user.
  • the lower lock server checks the lock status of the specific data portion D in the current data block lock information table. If the specific data portion D is not locked, the table is If the specific data portion D has not been locked by another program, the lock status of the specific data portion D is marked as locked in the data block lock status information table, and the lower data block server is notified to return the specific data portion D to the file request client; It should be noted that for the same data block, it will contain a lot of data information, and the file request client needs to lock only a few pages of the data information. Here, the data information is divided into a plurality of parts, and then the file requesting client needs to lock one of the plurality of parts.
  • the lower layer locking server When the lower layer locking server receives the write lock request for the specific data portion of the data block B sent by the file requesting client, the lower layer locking server checks the locking condition of the specific data portion in the current data block locking information table, if the specific data portion is not Locking, in the data block state information table, marking the locking state of the specific data portion as locking, and returning the file requesting client to the successful locking; if the specific data portion has been locked, using the corresponding locking failure policy, specifically Say, the lock failure policy includes lock failure or other strategies.
  • the file requesting client when the file requesting client receives the message that the specific data portion of the data block B is successfully locked, the message that the write lock is successful is returned to the operation user, and the user can perform the operation of starting writing or modifying the specific data portion of the data block B. It is. If the file requesting client receives a lock failure policy corresponding to the execution of the specific data portion of the data block B, the file request client may choose to wait for the lock to continue, or directly return the write lock failure to the operation user, at this time, the user does not have Permission to write to a specific data portion of block B.
  • the file request client checks the specific data portion locally before sending the read/write lock request or the write lock request to the specific data portion of the data block B to the lower layer data storage server C. Hits in the cache. If there is no specific data part in the local cache, that is, there is no data stored in the local cache requesting the client to lock the data, it is judged that the specific data block part is not hit, and the read/write lock request is sent to the lower layer lock server C; There is a specific data part, that is, the file requesting client performs a read operation or a write operation on the specific data portion of the data block B, but only the specific data portion has not been locked by the file request client at this time, and the J J judges the hit.
  • a specific data portion, and a write lock request is sent to the lower layer lock server C. That is to say, if a file client has previously performed a read operation or a write operation on a specific data block portion, when it requests the specific data portion again, it only needs to send a write lock request to the lower layer lock server.
  • FIG. 2 it is a flowchart of a method according to an embodiment of the present invention.
  • the file request client needs to lock the specific data portion of the data block B in the file A as an example, wherein Fac represents the file request client, and Fas represents the lower file system data server (including the lower layer data block server and The lower layer locks the server), and Fir represents the upper layer data location registration server.
  • Fac represents the file request client
  • Fas represents the lower file system data server (including the lower layer data block server and The lower layer locks the server)
  • Fir represents the upper layer data location registration server.
  • Fir receives the request information of the write open file A issued by the Fac and extracts the data block path information of the file A, that is, the chunk information. If Fir cannot extract the chunk information of the file A, Fir determines whether it is the first time to receive the Fac. The incoming request to open file A is written, and a unique complete chunk that can completely describe all the data blocks in file A is created for file A, and the chunk information is recorded. If Fir can extract the chunk information of file A, Fir directly extracts the chunk information of file A and returns it to Fac;
  • Fac determines the locking condition of the specific data part of the data block B in the local cache. If the specific data block part is in the local cache of the Fac and has been locked, go to step S4; if the specific data part is not locked, go to Step S5;
  • Fac sends a request for reading and writing a block data block B to a lower data storage server in the Fas;
  • S7 Fas checks whether the specific data portion of the current data block lock status information table data block B is locked. If not locked, the lower lock server marks the lock status of the specific data portion of the data block B in the data block lock status information table. To lock and return the specific data portion to the file request client; if it is locked, execute the lock failure policy;
  • Fac checks the status returned by Fas. If the specific data part is returned, the operation returns to the user that the lock is successful and starts writing. If the execution lock failure policy is received, the user may return the lock failure or wait for a while to continue. Request a lock.
  • Fac sends a request to the lower data storage server in the Fas to write a lock data block B specific data portion
  • S10 Fas checks whether the specific data portion of the current data block lock status information table data block B is locked. If not locked, the lower lock server marks the lock status of the specific data portion of the data block B in the data block lock status information table. To lock and return the lock to the file request client successfully; if it is locked, execute the lock failure policy;
  • Fac checks the status returned by Fas. If the return lock is successful, it returns the operation that the lock is successful and starts writing. If the lock execution failure policy is received, the lock failure may be returned to the user or wait for a period of time to continue to request the lock. .
  • the present invention also provides a write lock system for a distributed file system, comprising an upper layer data location registration selection path module, a lower layer data locking module and a lower layer data storage module disposed in the system;
  • the upper layer data location registration selection path module is configured to receive the file request client to send the write Opening a request for a file, and extracting data block path information of the file is returned to the file request client;
  • a lower layer data locking module configured to: according to the file requesting a lock request sent by a client to a specific data portion of a specific data block in the file, returning write lock authority information of the specific data portion of the specific data block to the File request client.
  • the file requesting client needs to lock the specific data portion of the data block B as an example for description.
  • the upper data location registration server divides the same file into multiple data blocks and stores them in the same or different lower file system data servers, usually in different file system data servers, specifically in the data block server. Inside. That is to say, there are many data blocks from different files stored in the same underlying file system data server. Once the upper data location registration server determines a unique complete data block path for a file, all file request clients need to lock a particular data portion of a data block in the file.
  • This unique block path is accessed and the corresponding lock operation is performed. That is to say, at this time, the lock permission of the data block has been distributed to the underlying file system data server.
  • the upper layer data location registration server receives the file request client's write request to open a file lock request, only the determined one copy data block path is selected, so that the load of the upper data location registration server is not raised by itself. Since then, write locks on a block of data in a distributed file system have nothing to do with the upper data location hosting server.
  • the locking system can be expanded with the expansion of the distributed file system, and thus has good scalability.
  • each of the other file request clients only needs to register with the upper layer data location. Once the server communicates once, the data block path information of the file where the data portion to be locked is located can be obtained. If the file requests the client to obtain the write lock permission of the data block again, the file request client only needs to send a lock request to the lower layer data storage server, and the write lock permission of the data block can be obtained from the lower lock server. This reduces the number of times the file request client communicates with the upper data location hosting server.
  • the write lock permission of the data block includes write lock permission of all data stored in the data block.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Information Transfer Between Computers (AREA)
  • Storage Device Security (AREA)

Abstract

La présente invention se rapporte à un procédé et à un procédé système de verrouillage en écriture pour un système de fichiers distribué. Le procédé selon l'invention comprend les étapes suivantes : quand un serveur d'enregistrement de positions de données de couche supérieure reçoit une demande émanant d'un client requérant un fichier, d'écrire dans un fichier ouvert, le serveur d'enregistrement de positions de données de couche supérieure extrait des données de chemin de bloc de données du fichier et retourne les données de chemin de bloc de données au client requérant un fichier ; sur la base d'une demande envoyée par le client requérant un fichier, de verrouiller une partie de données spécifique dans un bloc de données spécifique du fichier, un serveur de verrouillage de couche inférieure retourne des données d'autorisation de verrouillage en écriture de la partie de données spécifique du bloc de données spécifique au client requérant le fichier. La présente invention ne garantit pas seulement qu'une amélioration de la capacité de débit de la soumission de verrouillage dans le système de fichiers distribué puisse être obtenue sans devoir procéder à des investissements matériels. Elle garantit en outre un bon niveau d'extensibilité dans la mesure où une extension de capacité synchrone peut être réalisée quand l'extension de capacité du système de fichiers distribué est accomplie.
PCT/CN2011/083694 2010-12-20 2011-12-08 Procédé et système de verrouillage en écriture pour un système de fichiers distribué Ceased WO2012083797A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010596619.5 2010-12-20
CN201010596619.5A CN102088484B (zh) 2010-12-20 2010-12-20 一种分布式文件系统的写锁定方法及系统

Publications (1)

Publication Number Publication Date
WO2012083797A1 true WO2012083797A1 (fr) 2012-06-28

Family

ID=44100096

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/083694 Ceased WO2012083797A1 (fr) 2010-12-20 2011-12-08 Procédé et système de verrouillage en écriture pour un système de fichiers distribué

Country Status (2)

Country Link
CN (1) CN102088484B (fr)
WO (1) WO2012083797A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106559282A (zh) * 2015-09-29 2017-04-05 中兴通讯股份有限公司 一种锁定文件管理方法和装置

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102088484B (zh) * 2010-12-20 2014-12-10 南京中兴新软件有限责任公司 一种分布式文件系统的写锁定方法及系统
US8751493B2 (en) * 2012-04-23 2014-06-10 Google Inc. Associating a file type with an application in a network storage service
CN103095686B (zh) * 2012-12-19 2016-06-08 华为技术有限公司 热点元数据访问控制方法和服务器
CN104281442A (zh) * 2013-07-12 2015-01-14 富泰华工业（深圳）有限公司 文件处理系统及方法
CN104573428B (zh) * 2013-10-12 2018-02-13 方正宽带网络服务股份有限公司 一种提高服务器集群资源有效性的方法及系统
CN103647850B (zh) * 2013-12-25 2017-01-25 北京京东尚科信息技术有限公司 一种分布式版本控制系统的数据处理方法、设备及系统
CN105320512B (zh) * 2014-07-30 2019-08-06 腾讯科技（深圳）有限公司 分配主干权限的方法及装置
CN105681367A (zh) * 2014-11-17 2016-06-15 中国移动通信集团公司 一种共享文件内容的方法、服务器和客户端
CN105224255B (zh) * 2015-10-14 2018-10-30 浪潮(北京)电子信息产业有限公司 一种存储文件管理方法及装置
CN106855871B (zh) * 2015-12-09 2020-04-07 阿里巴巴集团控股有限公司 一种数据迁移的方法和装置
CN107146075B (zh) * 2016-03-01 2020-11-10 创新先进技术有限公司 请求处理方法及装置
CN108647285B (zh) * 2018-05-04 2021-06-22 北京小米移动软件有限公司 分布式文件系统中重命名方法、装置及分布式文件系统
CN111274208B (zh) * 2018-12-05 2023-06-30 杭州海康威视系统技术有限公司 锁定文件的方法和装置
CN116055565B (zh) * 2023-01-28 2023-06-06 北京蓝色星际科技股份有限公司 一种数据传输方法、系统、装置、电子设备及存储介质
CN116521632A (zh) * 2023-04-20 2023-08-01 远光软件股份有限公司 基于请求路径的缓存文件高并发读写处理方法、计算机装置、计算机可读存储介质
CN119336608B (zh) * 2024-12-18 2025-03-28 英诺达(成都)电子科技有限公司 测试用例文件的管理方法、装置及系统、电子设备、存储介质及程序产品

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6925515B2 (en) * 2001-05-07 2005-08-02 International Business Machines Corporation Producer/consumer locking system for efficient replication of file data
CN1771495A (zh) * 2003-05-07 2006-05-10 国际商业机器公司 分布式文件服务体系结构系统
CN101706802A (zh) * 2009-11-24 2010-05-12 成都市华为赛门铁克科技有限公司 一种数据写入、修改及恢复的方法、装置及服务器
CN102088484A (zh) * 2010-12-20 2011-06-08 南京中兴新软件有限责任公司 一种分布式文件系统的写锁定方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6925515B2 (en) * 2001-05-07 2005-08-02 International Business Machines Corporation Producer/consumer locking system for efficient replication of file data
CN1771495A (zh) * 2003-05-07 2006-05-10 国际商业机器公司 分布式文件服务体系结构系统
CN101706802A (zh) * 2009-11-24 2010-05-12 成都市华为赛门铁克科技有限公司 一种数据写入、修改及恢复的方法、装置及服务器
CN102088484A (zh) * 2010-12-20 2011-06-08 南京中兴新软件有限责任公司 一种分布式文件系统的写锁定方法及系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106559282A (zh) * 2015-09-29 2017-04-05 中兴通讯股份有限公司 一种锁定文件管理方法和装置
WO2017054734A1 (fr) * 2015-09-29 2017-04-06 中兴通讯股份有限公司 Procédé et dispositif de gestion de fichier de verrouillage

Also Published As

Publication number Publication date
CN102088484B (zh) 2014-12-10
CN102088484A (zh) 2011-06-08

Similar Documents

Publication Publication Date Title
WO2012083797A1 (fr) Procédé et système de verrouillage en écriture pour un système de fichiers distribué
US11895188B2 (en) Distributed storage system with web services client interface
US8086581B2 (en) Method for managing lock resources in a distributed storage system
US10805227B2 (en) System and method for controlling access to web services resources
JP6538780B2 (ja) 分散型データベースシステムのシステム全体のチェックポイント回避
CN105393243B (zh) 事务定序
CN1320483C (zh) 用于在多节点环境中实施日志处理的系统和方法
JP5059974B2 (ja) クラスタ共有ボリューム
US9076012B2 (en) Access requests with cache intentions
RU2686594C2 (ru) Файловая служба, использующая интерфейс совместного файлового доступа и передачи состояния представления
US9424140B1 (en) Providing data volume recovery access in a distributed data store to multiple recovery agents
JP6225262B2 (ja) 分散データグリッドにおいてデータを同期させるためにパーティションレベルジャーナリングをサポートするためのシステムおよび方法
US10708379B1 (en) Dynamic proxy for databases
CN107832423B (zh) 一种用于分布式文件系统的文件读写方法
CN106021327B (zh) 一种支持多用户同时读写的网盘系统及其读文件方法、写文件方法
CN117851363A (zh) 一种并行文件系统客户端高速缓存方法和系统
US7716307B1 (en) Method and apparatus for reducing client-server messages associated with opening a file
CN111966634A (zh) 一种文件操作方法、系统、设备以及介质
US7962600B2 (en) WAFS disconnected-mode read-write access
US11288112B1 (en) Enforcing data loss thresholds for performing updates to mirrored data sets
Li et al. Enabling the Write-Back Page Cache with Strong Consistency in Distributed Userspace File Systems
US12242505B1 (en) Recovering from interruptions in database replication streams
JP2011164885A (ja) ファイル格納プログラム、ファイル格納システム
CN100576848C (zh) 分布式数据动态程序代理方法
US12007954B1 (en) Selective forwarding for multi-statement database transactions

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11850730

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11850730

Country of ref document: EP

Kind code of ref document: A1