CN117112525A - Distributed file system and method for maintaining file consistency in distributed file system - Google Patents
Distributed file system and method for maintaining file consistency in distributed file system Download PDFInfo
- Publication number
- CN117112525A CN117112525A CN202311054571.9A CN202311054571A CN117112525A CN 117112525 A CN117112525 A CN 117112525A CN 202311054571 A CN202311054571 A CN 202311054571A CN 117112525 A CN117112525 A CN 117112525A
- Authority
- CN
- China
- Prior art keywords
- metadata
- lease
- consistency
- client
- server
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 52
- 238000011084 recovery Methods 0.000 claims description 9
- 238000004590 computer program Methods 0.000 claims description 7
- 230000007246 mechanism Effects 0.000 claims description 6
- 238000012545 processing Methods 0.000 claims description 6
- 238000012544 monitoring process Methods 0.000 claims description 5
- 230000000694 effects Effects 0.000 abstract 1
- 238000004891 communication Methods 0.000 description 12
- 238000010586 diagram Methods 0.000 description 4
- 230000009467 reduction Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- KLDZYURQCUYZBL-UHFFFAOYSA-N 2-[3-[(2-hydroxyphenyl)methylideneamino]propyliminomethyl]phenol Chemical compound OC1=CC=CC=C1C=NCCCN=CC1=CC=CC=C1O KLDZYURQCUYZBL-UHFFFAOYSA-N 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 201000001098 delayed sleep phase syndrome Diseases 0.000 description 1
- 208000033921 delayed sleep phase type circadian rhythm sleep disease Diseases 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- 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
-
- 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/11—File system administration, e.g. details of archiving or snapshots
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)
Abstract
The application relates to a distributed file system and a method for maintaining file consistency in the distributed file system, which are applied to the technical field of computer systems, wherein the method is applied to a client and comprises the following steps: the client receives the file access request and sends a consistency lease request and a metadata acquisition request to the metadata server; receiving a consistency lease and metadata sent by a metadata server; acquiring data to be written of a file access request; generating updated metadata based on the data to be written and the metadata updated metadata; generating a writing request based on the updating metadata and the data to be written, and sending the writing request to a data server; judging whether the writing is successful or not according to the feedback information of the data server; if the writing is successful, the client side updates the metadata server based on the updated metadata; if the writing fails, generating writing failure information. The application has the effect of realizing the lightweight file consistency method without reducing the performance and increasing the cost.
Description
Technical Field
The present application relates to the field of computer systems, and in particular, to a distributed file system and a method for maintaining file consistency in the distributed file system.
Background
In the computer arts, a file system refers to a set of rules and structures for managing files and directories stored on a computer. In a file system, in order to ensure correctness and stability of the file system, the file system needs to modify data and metadata of a file at the same time, and usually the file system uses a transaction mechanism or copy-on-write to ensure consistency of the metadata and the data.
Unlike a conventional stand-alone file system, a distributed file system is a system for sharing and managing files in a distributed computing environment that achieves data scalability, high availability, and fault tolerance by distributing the files and associated metadata across multiple computing nodes.
Storing metadata and data in different locations means that it must be ensured that they remain synchronized, which if they are inconsistent, can lead to system failure or data corruption, and thus, distributed systems are typically implemented using Two-Phase Commit protocols Two-Phase Commit and 2 PC. However, there are still problems of cumbersome implementation, high cost, and more communication interactions, and there is a need for a lightweight file consistency method that does not reduce performance and increase cost.
Disclosure of Invention
In order to realize a lightweight file consistency method without reducing performance and increasing cost, the application provides a distributed file system and a method for maintaining file consistency in the distributed file system.
In a first aspect, the present application provides a distributed file system, which adopts the following technical scheme:
a distributed file system, comprising:
the client is used for receiving the file access request, processing metadata and data;
a metadata server for providing and storing metadata;
and the data server is used for providing and storing data.
By adopting the technical scheme, the metadata and the data are stored separately in a three-terminal management mode, the client terminal manages and controls the metadata server and the data server, and the metadata and the data are updated according to the file access request, so that the lightweight file consistency without performance reduction and cost increase is realized.
In a second aspect, the present application provides a method for maintaining file consistency in a distributed file system, which adopts the following technical scheme:
a method for maintaining file consistency in a distributed file system, applied to a client, the method comprising:
the client receives the file access request and sends a consistency lease request and a metadata acquisition request to the metadata server;
receiving a consistency lease and metadata sent by the metadata server;
acquiring data to be written of the file access request;
updating the metadata based on the data to be written and the metadata, and generating updated metadata;
generating a write request based on the update metadata and the data to be written, and sending the write request to the data server;
judging whether the writing is successful or not according to the feedback information of the data server;
if the writing is successful, the client updates the metadata server based on the updated metadata;
if the writing fails, generating writing failure information.
By adopting the technical scheme, the metadata and the data are stored separately in a three-terminal management mode, the client terminal manages and controls the metadata server and the data server, and the metadata and the data are updated according to the file access request, so that the lightweight file consistency without performance reduction and cost increase is realized.
Optionally, the method further comprises:
acquiring the grant time and the grant duration of the consistency lease;
judging whether the consistency constraint reaches a preset duration time or not based on the grant time and the grant time length;
and if the consistency constraint reaches the preset duration time, sending a lease extension request to the metadata server based on a heartbeat mechanism.
In a third aspect, the present application provides a method for maintaining file consistency in a distributed file system, which adopts the following technical scheme:
a method for maintaining file consistency in a distributed file system, applied to a metadata server, the method comprising:
responding to a consistency lease request and a metadata acquisition request sent by the client, sending a consistency lease and metadata to the client, and sending a lease version number of the consistency lease to the data server;
monitoring the heartbeat of the client in real time;
judging whether the heartbeat is out of date;
if the heartbeat is out of date, entering a recovery flow;
and if the heartbeat is not expired, repeating the step of monitoring the heartbeat of the client in real time.
By adopting the technical scheme, the metadata and the data are stored separately in a three-terminal management mode, the client terminal manages and controls the metadata server and the data server, and the metadata and the data are updated according to the file access request, so that the lightweight file consistency without performance reduction and cost increase is realized.
Optionally, the entering the recovery procedure includes:
the metadata server forcibly reclaims the coherence lease sent to the client and does not grant a new coherence lease to the client;
the metadata server changes the lease version number of the consistency lease and synchronizes the changed lease version number to the data server;
the metadata server opens the grant of the consistency lease and grants the consistency lease to other clients;
the metadata server requests the newly granted client to read the latest metadata in the data server based on the version number leased with the coherence.
In a fourth aspect, the present application provides a method for maintaining file consistency in a distributed file system, which adopts the following technical scheme:
a method for maintaining file consistency in a distributed file system, applied to a data server, the method comprising:
receiving a lease version number sent by the metadata server;
responding to a writing request sent by the client, and acquiring a lease version number of a consistency lease of the client;
judging whether the two lease version numbers are the same;
if the two lease version numbers are the same, writing the update metadata and the data to be written;
and if the two lease version numbers are different, rejecting the write request.
By adopting the technical scheme, the metadata and the data are stored separately in a three-terminal management mode, the client terminal manages and controls the metadata server and the data server, and the metadata and the data are updated according to the file access request, so that the lightweight file consistency without performance reduction and cost increase is realized.
In a fifth aspect, the present application provides an electronic device, which adopts the following technical scheme:
an electronic device comprising a processor coupled with a memory;
the processor is configured to execute a computer program stored in the memory, so that the electronic device executes the computer program for maintaining a file consistency method in the distributed file system according to any one of the second aspects.
In a sixth aspect, the present application provides a computer readable storage medium, which adopts the following technical scheme:
a computer readable storage medium storing a computer program capable of being loaded by a processor and executing the method of maintaining file consistency in a distributed file system according to any of the second aspects.
Drawings
FIG. 1 is a block diagram of a distributed file system according to an embodiment of the present application.
Fig. 2 is a flowchart of a method for maintaining file consistency in a distributed file system applied to a client according to an embodiment of the present application.
Fig. 3 is a flowchart of a method for maintaining file consistency in a distributed file system applied to a metadata server according to an embodiment of the present application.
Fig. 4 is a flowchart of a method for maintaining file consistency in a distributed file system applied to a data server according to an embodiment of the present application.
Fig. 5 is a block diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The present application will be described in further detail with reference to the accompanying drawings.
Fig. 1 is a block diagram of a distributed file system 100 according to an embodiment of the present application.
As shown in fig. 1, the distributed file system 100 mainly includes:
a client 100 for receiving a file access request, processing metadata and data;
a metadata server 200 for providing and storing metadata;
the data server 300 is used for providing and storing data.
In this embodiment, a three-terminal management manner is adopted to store the file, metadata is stored in a metadata server, data is stored in a data server, the metadata server and the data server are respectively managed through a client, and all data is stored in the data server and the metadata server after being processed by the client, so that file consistency is realized on the basis of not reducing performance and not increasing cost.
The embodiment of the application provides a method for maintaining file consistency in a distributed file system, which can be executed by electronic equipment, wherein the electronic equipment can be a server or terminal equipment, and the server can be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server for providing cloud computing service. The terminal device may be, but is not limited to, a smart phone, a tablet computer, a desktop computer, etc.
Fig. 2 is a flow chart of a method for maintaining file consistency in a distributed file system applied to a client according to an embodiment of the present application.
As shown in fig. 2, the main flow of the method is described as follows (steps S401 to S408):
in step S401, the client receives the file access request, and sends a consistency lease request and a metadata acquisition request to the metadata server.
In this embodiment, when a user operates a file, the system generates a file access request, and when the client receives the file access request, the client indicates that the data may be about to be modified, and needs to perform update operation on metadata and data, at this time, a consistency lease request and a metadata request need to be sent to a metadata server, so as to obtain consistency lease and metadata, and update processing of the metadata and the data is performed according to the obtained metadata. It should be noted that only clients holding a coherence lease can make file access, and file access requests include, but are not limited to, write, read, etc.
Step S402, receiving the consistency lease and the metadata sent by the metadata server.
In this embodiment, the coherence lease is a file license acquired by a server from a metadata server, and only the server with the coherence lease can access a file, that is, only after the server obtains the coherence lease, the server can access the file corresponding to the initiated file access request after the user initiates the access request. If a plurality of clients are arranged in a system, only one client can acquire a consistency lease in order to ensure the accuracy of data synchronization when the file access is carried out, and after the client with the consistency lease gives up the consistency lease, other clients can acquire the consistency lease.
Step S403, obtain the data to be written of the file access request.
In this embodiment, when a user initiates a file access request, it indicates that a read-write operation needs to be performed on a file, and when a write operation needs to be performed on the user, it indicates that data in a data server and metadata in a metadata server need to be modified, so that the metadata and the data remain synchronized.
Step S404, update metadata is generated based on the data to be written and the metadata update metadata.
In this embodiment, when new data is generated, the generated new data is used as data to be written, metadata is updated according to the currently generated data to be written and metadata acquired from a metadata server, that is, the acquired metadata is updated, and updated metadata is generated. The update operation at this time is not performed in the metadata server, but performed in the server.
Step S405, a write request is generated based on the update metadata and the data to be written, and the write request is sent to the data server.
In this embodiment, after generating the update metadata, the client needs to write both the update source data and the data to be written into the data server together, so as to generate a write request according to the update metadata and the data to be written, send the write request to the data server, and wait for feedback that the data server performs writing successfully.
In step S406, it is determined whether the writing is successful in response to the feedback information of the data server.
In this embodiment, the write feedback duration is set, timing is started after the write request is sent to the data server, and when the write success feedback sent by the data server is received within the write feedback duration, the timing is stopped, and it is determined that the write is successful. And if the feedback information sent by the data server is not received within the writing feedback time length, namely, the feedback of the writing success is not received, judging that the writing fails.
In step S407, if the writing is successful, the client updates the metadata server based on the updated metadata.
In this embodiment, if the data server updates the metadata and writes the metadata to the data to be written successfully, the data update is successful, and in order to ensure consistency of the data and the metadata, the metadata needs to be updated after the data update is successful, and at this time, the client controls the metadata server to update the metadata according to the updated metadata.
In step S408, if the writing fails, writing failure information is generated.
In this embodiment, if the writing of the data server fails, the writing failure information may be generated according to the writing time length, and the writing failure information may be fed back to the user. And the metadata server can also request the client to feed back the latest metadata, the client reads the data information in the data server, judges whether the writing is successful or not and feeds back the latest metadata according to the data information, if the writing is successful or not, the metadata follow-up operation is performed according to the metadata, and if the writing is not successful, the writing failure information is generated according to the writing time.
In this embodiment, a coherence lease grant time and a grant duration are obtained; judging whether the consistency constraint reaches a preset renewal time or not based on the grant time and the grant time length; and if the consistency constraint reaches the preset duration time, sending a lease extension request to the metadata server based on a heartbeat mechanism.
The consistency lease has time limit, when the grant duration is reached, the metadata server will reclaim the consistency lease granted to the client, for the client, after obtaining the consistency lease sent by the cloud data server, the client needs to count the authority possession time according to the grant time and the grant duration, when reaching the preset duration, the client needs to judge whether the continuation of the consistency lease needs to be carried out according to the self requirement, and if the continuation needs to be carried out, the client sends a lease extension request to the metadata server according to a heartbeat mechanism. It should be noted that, the grant duration is also recorded by using a heartbeat mechanism, and the reserved duration is also set by using heartbeats as a period, for example, the grant duration is 5 heartbeat periods, the preset duration may be set to 4 heartbeat periods, and when the 4 th heartbeat period is over, the preset duration is reached, and the preset duration needs to be set according to actual requirements, which is not limited specifically herein.
Fig. 3 is a flowchart of a method for maintaining file consistency in a distributed file system applied to a metadata server according to an embodiment of the present application.
As shown in fig. 3, the main flow of the method is described as follows (steps S501 to S505):
in step S501, in response to the coherence lease request and the metadata acquisition request sent by the client, coherence lease and metadata are sent to the client, and a lease version number of the coherence lease is sent to the data server.
In this embodiment, after receiving a coherence lease request sent by a client, a metadata server grants a coherence lease to the client that sends the coherence lease, and sends the granted coherence lease and metadata to the client together, and in order to ensure that the client can access a file, it is necessary to send a lease version number of the coherence lease sent to the client to a data server, so that the data server verifies according to the lease version number.
Step S502, the heartbeat of the client is monitored in real time.
In this embodiment, the metadata server also records the duration of lease grant, monitors the heartbeat of the client in real time and records it after the lease grant consistency, for example, after the first heartbeat cycle ends, the heartbeat of the client records as 1, indicating that the client has used the lease consistency for one heartbeat cycle.
Step S503, judging whether the heartbeat is out of date.
In this embodiment, the detection and judgment operations are performed in real time, and the heartbeat expiration judgment operation is performed after the client heartbeat is obtained.
Step S504, if the heartbeat is out of date, the recovery flow is entered.
For step S504, the metadata server forcibly reclaims the coherence lease sent to the client and does not grant a new coherence lease to the client; the metadata server changes the lease version number of the consistency lease and synchronizes the changed lease version number to the data server; the metadata server opens a grant of a consistency lease and grants the consistency lease to other clients; the metadata server requests the newly granted client to read the latest metadata in the data server based on the version number leased with the coherence.
In this embodiment, if the heartbeat expires, the metadata server will enter the recovery process after the current operation is completed. The recovery process mainly includes four steps, the first step is the most important step, namely, the metadata server grants a forced recovery to the coherence lease of the client after the heart-skip period, and does not continue to send a new coherence lease to the client recovering the coherence lease, the client recovering the coherence lease described herein does not continue to send a new coherence lease, and does not send a new coherence lease immediately after recovery, if the client still sends a coherence lease request in the subsequent process, the metadata server still sends a coherence lease to the client.
The second step is to change the lease version number of the consistency lease, and send the changed lease version number to the data server, when a new update operation is required to be generated after the lease version number is changed, the changed lease version number is sent to the data server, so that the client server verifies the lease version number, and a new connection is established between the client server and the client.
The third step is that the metadata server opens a grant of the coherence lease, grants the coherence lease to other clients, i.e. after forcing the coherence lease to be withdrawn, continues to receive grant requests from other clients, and grants the coherence lease to other clients.
And a fourth step, the metadata server reads the latest metadata in the data server based on the newly granted client requested by the version number of the coherence lease, namely, the updating step is continued, the data in the data server corresponding to the client which reestablishes the connection is read, the latest metadata is generated, and accordingly the latest metadata is written into the metadata server, and if the client has a problem, the latest metadata is not written into the metadata server.
In step S505, if the heartbeat is not expired, the step of monitoring the heartbeat of the client in real time is repeated.
Fig. 4 is a flowchart of a method for maintaining file consistency in a distributed file system applied to a data server according to an embodiment of the present application.
As shown in fig. 4, the main flow of the method is described as follows (steps S601 to S605):
step S601, a lease version number sent by a metadata server is received;
step S602, responding to a writing request sent by a client, and acquiring a lease version number of a consistency lease of the client;
step S603, judging whether the two lease version numbers are the same;
step S604, if the two lease version numbers are the same, the update metadata and the data to be written are written;
in step S605, if the two lease version numbers are different, the write request is denied.
In this embodiment, after obtaining the lease version number and receiving the write request of the client, the data server verifies whether the lease version number of the client consistency lease is the same as the lease version number owned by the client, if so, it indicates that a connection is established with the client, and a write operation can be performed, and after successful write, a feedback of the write success is performed to the client, and if not, the write request of the client is directly denied.
Fig. 5 is a block diagram of an electronic device 700 according to an embodiment of the present application.
As shown in FIG. 5, the electronic device 700 includes a processor 701 and memory 702, and may further include an information input/information output (I/O) interface 703, one or more of a communication component 704, and a communication bus 705.
Wherein the processor 701 is configured to control the overall operation of the electronic device 700 to perform all or part of the steps of the method for maintaining file consistency in the distributed file system described above; the memory 702 is used to store various types of data to support operation on the electronic device 700, which may include, for example, instructions for any application or method operating on the electronic device 700, as well as application-related data. The Memory 702 may be implemented by any type or combination of volatile or non-volatile Memory devices, such as one or more of static random access Memory (Static Random Access Memory, SRAM), electrically erasable programmable Read-Only Memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), erasable programmable Read-Only Memory (Erasable Programmable Read-Only Memory, EPROM), programmable Read-Only Memory (Programmable Read-Only Memory, PROM), read-Only Memory (ROM), magnetic Memory, flash Memory, magnetic disk, or optical disk.
The I/O interface 703 provides an interface between the processor 701 and other interface modules, which may be a keyboard, mouse, buttons, etc. These buttons may be virtual buttons or physical buttons. The communication component 704 is used for wired or wireless communication between the electronic device 700 and other devices. Wireless communication, such as Wi-Fi, bluetooth, near field communication (Near Field Communication, NFC for short), 2G, 3G or 4G, or a combination of one or more thereof, the corresponding communication component 104 may thus comprise: wi-Fi part, bluetooth part, NFC part.
The electronic device 700 may be implemented by one or more application specific integrated circuits (Application Specific Integrated Circuit, abbreviated ASIC), digital signal processors (Digital Signal Processor, abbreviated DSP), digital signal processing devices (Digital Signal Processing Device, abbreviated DSPD), programmable logic devices (Programmable Logic Device, abbreviated PLD), field programmable gate arrays (Field Programmable Gate Array, abbreviated FPGA), controllers, microcontrollers, microprocessors, or other electronic components for performing the method of maintaining file consistency in a distributed file system as set forth in the above embodiments.
Communication bus 705 may include a path to transfer information between the above components. The communication bus 705 may be a PCI (Peripheral Component Interconnect, peripheral component interconnect standard) bus or an EISA (Extended Industry Standard Architecture ) bus, or the like. The communication bus 705 may be divided into an address bus, a data bus, a control bus, and the like.
The electronic device 700 may include, but is not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), car terminals (e.g., car navigation terminals), and the like, and fixed terminals such as digital TVs, desktop computers, and the like, and may also be a server, and the like.
The application also provides a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program realizes the steps of the method for maintaining file consistency in the distributed file system when being executed by a processor.
The computer readable storage medium may include: a U-disk, a removable hard disk, a read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
The above description is only illustrative of the preferred embodiments of the present application and of the principles of the technology employed. It will be appreciated by persons skilled in the art that the scope of the application is not limited to the specific combinations of the features described above, but also covers other embodiments which may be formed by any combination of the features described above or their equivalents without departing from the spirit of the application. Such as the above-mentioned features and the technical features having similar functions (but not limited to) applied for in the present application are replaced with each other.
Claims (8)
1. A distributed file system, comprising:
the client is used for receiving the file access request, processing metadata and data;
a metadata server for providing and storing metadata;
and the data server is used for providing and storing data.
2. A method for maintaining file consistency in a distributed file system, the method comprising:
the client receives the file access request and sends a consistency lease request and a metadata acquisition request to the metadata server;
receiving a consistency lease and metadata sent by the metadata server;
acquiring data to be written of the file access request;
updating the metadata based on the data to be written and the metadata, and generating updated metadata;
generating a write request based on the update metadata and the data to be written, and sending the write request to the data server;
judging whether the writing is successful or not according to the feedback information of the data server;
if the writing is successful, the client updates the metadata server based on the updated metadata;
if the writing fails, generating writing failure information.
3. The method as recited in claim 2, further comprising:
acquiring the grant time and the grant duration of the consistency lease;
judging whether the consistency constraint reaches a preset duration time or not based on the grant time and the grant time length;
and if the consistency constraint reaches the preset duration time, sending a lease extension request to the metadata server based on a heartbeat mechanism.
4. A method for maintaining file consistency in a distributed file system, the method comprising, applied to a metadata server:
responding to a consistency lease request and a metadata acquisition request sent by the client, sending a consistency lease and metadata to the client, and sending a lease version number of the consistency lease to the data server;
monitoring the heartbeat of the client in real time;
judging whether the heartbeat is out of date;
if the heartbeat is out of date, entering a recovery flow;
and if the heartbeat is not expired, repeating the step of monitoring the heartbeat of the client in real time.
5. The method of claim 4, wherein the entering a recovery procedure comprises:
the metadata server forcibly reclaims the coherence lease sent to the client and does not grant a new coherence lease to the client;
the metadata server changes the lease version number of the consistency lease and synchronizes the changed lease version number to the data server;
the metadata server opens the grant of the consistency lease and grants the consistency lease to other clients;
the metadata server requests the newly granted client to read the latest metadata in the data server based on the version number leased with the coherence.
6. A method for maintaining file consistency in a distributed file system, the method comprising:
receiving a lease version number sent by the metadata server;
responding to a writing request sent by the client, and acquiring a lease version number of a consistency lease of the client;
judging whether the two lease version numbers are the same;
if the two lease version numbers are the same, writing the update metadata and the data to be written;
and if the two lease version numbers are different, rejecting the write request.
7. An electronic device comprising a processor coupled to a memory;
the processor is configured to execute a computer program stored in the memory to cause the electronic device to perform the method of any one of claims 2 to 6.
8. A computer readable storage medium comprising a computer program or instructions which, when run on a computer, cause the computer to perform the method of any of claims 2 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311054571.9A CN117112525A (en) | 2023-08-21 | 2023-08-21 | Distributed file system and method for maintaining file consistency in distributed file system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311054571.9A CN117112525A (en) | 2023-08-21 | 2023-08-21 | Distributed file system and method for maintaining file consistency in distributed file system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117112525A true CN117112525A (en) | 2023-11-24 |
Family
ID=88797718
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311054571.9A Pending CN117112525A (en) | 2023-08-21 | 2023-08-21 | Distributed file system and method for maintaining file consistency in distributed file system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117112525A (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020152214A1 (en) * | 2001-04-17 | 2002-10-17 | Muntz Daniel A. | Lease enforcement in a distributed file system |
| US6775703B1 (en) * | 2000-05-01 | 2004-08-10 | International Business Machines Corporation | Lease based safety protocol for distributed system with multiple networks |
| CN102420854A (en) * | 2011-11-14 | 2012-04-18 | 西安电子科技大学 | Distributed file system facing to cloud storage |
| CN102546751A (en) * | 2011-12-06 | 2012-07-04 | 华中科技大学 | Hierarchical metadata cache control method of distributed file system |
| CN104158897A (en) * | 2014-08-25 | 2014-11-19 | 曙光信息产业股份有限公司 | Updating method of file layout in distributed file system |
| CN104516967A (en) * | 2014-12-25 | 2015-04-15 | 国家电网公司 | Electric power system mass data management system and use method thereof |
| CN107832423A (en) * | 2017-11-13 | 2018-03-23 | 中山大学 | A kind of file read/write method for distributed file system |
| CN110334072A (en) * | 2018-03-22 | 2019-10-15 | 腾讯科技（深圳）有限公司 | A kind of distributed file system, file updating method and device |
| CN111158597A (en) * | 2019-12-28 | 2020-05-15 | 浪潮电子信息产业股份有限公司 | Metadata reading method and device, electronic equipment and storage medium |
| CN116185962A (en) * | 2022-12-16 | 2023-05-30 | 中国联合网络通信集团有限公司 | Data processing method and device based on distributed file system |
-
2023
- 2023-08-21 CN CN202311054571.9A patent/CN117112525A/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6775703B1 (en) * | 2000-05-01 | 2004-08-10 | International Business Machines Corporation | Lease based safety protocol for distributed system with multiple networks |
| US20020152214A1 (en) * | 2001-04-17 | 2002-10-17 | Muntz Daniel A. | Lease enforcement in a distributed file system |
| CN102420854A (en) * | 2011-11-14 | 2012-04-18 | 西安电子科技大学 | Distributed file system facing to cloud storage |
| CN102546751A (en) * | 2011-12-06 | 2012-07-04 | 华中科技大学 | Hierarchical metadata cache control method of distributed file system |
| CN104158897A (en) * | 2014-08-25 | 2014-11-19 | 曙光信息产业股份有限公司 | Updating method of file layout in distributed file system |
| CN104516967A (en) * | 2014-12-25 | 2015-04-15 | 国家电网公司 | Electric power system mass data management system and use method thereof |
| CN107832423A (en) * | 2017-11-13 | 2018-03-23 | 中山大学 | A kind of file read/write method for distributed file system |
| CN110334072A (en) * | 2018-03-22 | 2019-10-15 | 腾讯科技（深圳）有限公司 | A kind of distributed file system, file updating method and device |
| CN111158597A (en) * | 2019-12-28 | 2020-05-15 | 浪潮电子信息产业股份有限公司 | Metadata reading method and device, electronic equipment and storage medium |
| CN116185962A (en) * | 2022-12-16 | 2023-05-30 | 中国联合网络通信集团有限公司 | Data processing method and device based on distributed file system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP5727020B2 (en) | Cloud computing system and data synchronization method thereof | |
| CN111274252B (en) | Block chain data uplink method and device, storage medium and server | |
| US10089187B1 (en) | Scalable cloud backup | |
| US10331625B2 (en) | Managing sequential data store | |
| EP2933733A1 (en) | Data processing method and device in distributed file storage system | |
| US11093290B1 (en) | Backup server resource-aware discovery of client application resources | |
| CN109684270A (en) | Database filing method, apparatus, system, equipment and readable storage medium storing program for executing | |
| US11321193B2 (en) | Database restoration across cloud environments | |
| CN111866129B (en) | Method, device and medium for determining service availability index based on cloud platform | |
| CN117520278A (en) | Multi-client high-precision directory quota control method for distributed file system | |
| US10922190B1 (en) | Updating database records while maintaining accessible temporal history | |
| CN117112525A (en) | Distributed file system and method for maintaining file consistency in distributed file system | |
| CN113872994B (en) | Organization architecture synchronization method, device, computer equipment and storage medium | |
| CN110022348B (en) | System and method for dynamic backup sessions | |
| CN115390754A (en) | Hard disk management method and device | |
| US9971532B2 (en) | GUID partition table based hidden data store system | |
| CN113672640A (en) | Data query method and device, computer equipment and storage medium | |
| CN114930315A (en) | Processing delete requests based on updated change summaries | |
| CN113761075A (en) | Method, device, equipment and computer readable medium for switching databases | |
| CN112235332A (en) | Read-write switching method and device for cluster | |
| US10860668B1 (en) | Querying system and method | |
| US10938919B1 (en) | Registering client devices with backup servers using domain name service records | |
| CN117009294B (en) | Method for implementing consistency snapshot in distributed file system | |
| CN113868679B (en) | Cluster encryption method and device | |
| CN108733822A (en) | A kind of file memory method, device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |