CN109165112B - Fault recovery method, system and related components of metadata cluster - Google Patents
Fault recovery method, system and related components of metadata cluster Download PDFInfo
- Publication number
- CN109165112B CN109165112B CN201810934272.7A CN201810934272A CN109165112B CN 109165112 B CN109165112 B CN 109165112B CN 201810934272 A CN201810934272 A CN 201810934272A CN 109165112 B CN109165112 B CN 109165112B
- Authority
- CN
- China
- Prior art keywords
- metadata
- inode
- failure
- service
- cluster
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 38
- 238000011084 recovery Methods 0.000 title claims abstract description 32
- 238000004891 communication Methods 0.000 claims abstract description 11
- 238000004590 computer program Methods 0.000 claims description 10
- 238000001514 detection method Methods 0.000 claims description 2
- 230000009286 beneficial effect Effects 0.000 abstract description 2
- 230000004048 modification Effects 0.000 description 7
- 238000012986 modification Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0709—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0793—Remedial or corrective actions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1435—Saving, restoring, recovering or retrying at system level using file system or storage system metadata
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Library & Information Science (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a failure recovery method of a metadata cluster, which comprises the steps of determining a failure metadata service in the metadata cluster when the metadata cluster is detected to have a failure; inquiring a standby metadata service corresponding to the failure metadata service, and establishing communication connection between all clients and the standby metadata service; transmitting target inode information in an operation file list of each client to the standby metadata service so that the metadata cluster recovers external services; and the target inode information is the inode information used by the client at the current moment. The method can reduce the loading time of the inode information and improve the efficiency of the metadata service fault recovery when the metadata service fault is recovered. The application also discloses a metadata cluster fault recovery system, a computer readable storage medium and an electronic device, which have the beneficial effects.
Description
Technical Field
The present invention relates to the field of data storage management, and in particular, to a method and a system for recovering a failure of a metadata cluster, a computer-readable storage medium, and an electronic device.
Background
When the metadata cluster fails, the standby metadata service takes over the failed metadata service, and the cluster external service is recovered. During this recovery period, the successor metadata service does not serve the outsides, i.e., does not respond to client requests. The length of the recovery time directly affects the user experience.
In the prior art, during the recovery of a metadata cluster failure, a connection needs to be reestablished with a client, and all clients send all inode (index node) information in the existing cache to the standby metadata service, so that the standby metadata service loads the inode information into a memory. However, the amount of inode information in the existing cache of the client is huge, and if the metadata is completely loaded, the failure recovery time is increased.
Therefore, how to reduce the loading time of the inode information and improve the efficiency of metadata service failure recovery when metadata service failure recovery is a technical problem that needs to be solved by those skilled in the art at present.
Disclosure of Invention
The present application is directed to a method and a system for recovering a failure of a metadata cluster, a computer-readable storage medium, and an electronic device, which are capable of reducing loading time of inode information and improving efficiency of recovering a metadata service failure when the metadata service failure is recovered.
In order to solve the above technical problem, the present application provides a method for recovering a failure of a metadata cluster, where the method for recovering a failure includes:
when a metadata cluster is detected to be out of order, determining a failure metadata service in the metadata cluster;
inquiring a standby metadata service corresponding to the failure metadata service, and establishing communication connection between all clients and the standby metadata service;
transmitting target inode information in the operation file list of each client to the standby metadata service so that the metadata cluster recovers external services; the target inode information is the inode information used by the client at the current moment.
Optionally, the method further includes:
and inquiring the inode holding authority of each client, and generating the operation file list according to the inode information corresponding to the inode holding authority as the target inode information.
Optionally, the inode holding permission includes an inode opening permission and/or an inode modification attribute field permission.
Optionally, after the metadata cluster recovers the external service, the method further includes:
and uploading prompt information of the failure metadata service downtime.
The present application further provides a metadata cluster failover system, comprising:
the metadata cluster failure detection module is used for detecting the failure of a metadata cluster, and determining the failure metadata service in the metadata cluster;
the redundancy module is used for inquiring the standby metadata service corresponding to the failure metadata service and establishing communication connection between all the clients and the standby metadata service;
the failure recovery module is used for transmitting target inode information in the operation file list of each client to the standby metadata service so that the metadata cluster can recover external services; the target inode information is the inode information used by the client at the current moment.
Optionally, the method further includes:
and the list generation module is used for inquiring the inode holding authority of each client and generating the operation file list according to the inode information corresponding to the inode holding authority as the target inode information.
Optionally, the inode holding permission includes an inode opening permission and/or an inode modification attribute field permission.
Optionally, the method further includes:
and the fault prompting module is used for uploading the prompting information of the failure metadata service downtime.
The present application further provides a computer-readable storage medium having stored thereon a computer program that, when executed, performs the steps performed by the above-described method for failure recovery of a metadata cluster.
The application also provides an electronic device, which comprises a memory and a processor, wherein the memory stores a computer program, and the processor realizes the steps executed by the fault recovery method of the metadata cluster when calling the computer program in the memory.
The invention provides a failure recovery method of a metadata cluster, which comprises the steps of determining a failure metadata service in the metadata cluster when the metadata cluster is detected to have a failure; inquiring a standby metadata service corresponding to the failure metadata service, and establishing communication connection between all clients and the standby metadata service; transmitting target inode information in the operation file list of each client to the standby metadata service so that the metadata cluster recovers external services; the target inode information is the inode information used by the client at the current moment.
According to the method and the device, only the inode information used by the client is transmitted to the standby metadata service when the metadata service fault is recovered, so that the content required to be loaded by the standby metadata service is reduced, the time for recovering the metadata service fault is shortened, and the metadata cluster can rapidly provide the service to the outside. Further, since the inode information in use in the client is transmitted to the standby metadata service, after the metadata service is recovered due to failure, the standby metadata service establishing a connection relationship with the client can provide normal service for the client, and the condition that the inode information in use by the client is not loaded into the metadata service cache is avoided. According to the method and the device, when the metadata service fault is recovered, the loading time of the inode information is shortened, and the efficiency of the metadata service fault recovery is improved. The application also provides a metadata cluster fault recovery system, a computer readable storage medium and an electronic device, which have the beneficial effects and are not described herein again.
Drawings
In order to more clearly illustrate the embodiments of the present application, the drawings needed for the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings can be obtained by those skilled in the art without inventive effort.
Fig. 1 is a flowchart of a method for recovering from a failure of a metadata cluster according to an embodiment of the present disclosure;
FIG. 2 is a flowchart of another method for recovering from a failure of a metadata cluster according to an embodiment of the present disclosure;
fig. 3 is a schematic structural diagram of a metadata cluster failure recovery system according to an embodiment of the present disclosure.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a flowchart of a method for recovering from a failure of a metadata cluster according to an embodiment of the present disclosure.
The specific steps may include:
s101: when a metadata cluster is detected to be out of order, determining a failure metadata service in the metadata cluster;
the embodiment is an implementation manner of how to implement fast failure recovery when a metadata cluster fails. The metadata cluster can comprise a plurality of metadata services, namely a metadata service which is in business interaction with the client and a standby redundant metadata service; a metadata service may be understood as a process. Since there are multiple metadata services in the metadata cluster, when a metadata cluster fails, this step first determines which metadata service has failed, i.e., determines the failed metadata service in the metadata cluster in this step, and the number of failed metadata services is not limited herein. It should be noted that, in this embodiment, only the service that performs business interaction with the client before the failure occurs and the failure metadata service occurs is referred to as the failure metadata service.
S102: inquiring a standby metadata service corresponding to the failure metadata service, and establishing communication connection between all clients and the standby metadata service;
in this embodiment, the standby metadata service may be used to replace the used metadata service, or there may be a correspondence between some used metadata services and the standby metadata service, and the standby metadata service corresponding to the failed metadata service is queried according to the correspondence. In summary, after determining that the backup metadata service capable of taking over the failure metadata service is available, all clients corresponding to the metadata cluster establish communication connection with the backup metadata service, so that all clients transmit necessary inode information to the backup metadata service.
S103: transmitting target inode information in the operation file list of each client to the standby metadata service so that the metadata cluster recovers external services; the target inode information is the inode information used by the client at the current moment.
Since the memory of the standby metadata service does not have the inode information in the client cache, the inode information in the client needs to be transmitted to the standby metadata service. In the prior art, all the inode information of the client is transmitted to the standby metadata service, but the fault recovery efficiency is affected due to the large data volume of all the inode information. In this embodiment, the standby metadata service is used in inode information transmission of a client at the current time, and the specific current time may be a time when the client establishes a communication connection with the standby metadata service.
It should be noted that the operation file list of the client stores the inode information currently used by the client at the current time, and sets the inode information currently used as the target inode information.
According to the embodiment, when the metadata service is recovered from a fault, only the inode information used by the client is transmitted to the standby metadata service, so that the content to be loaded by the standby metadata service is reduced, the time for recovering the fault of the metadata service is shortened, and the metadata cluster can rapidly provide the service to the outside. Further, since the inode information being used in the client is transmitted to the standby metadata service in the embodiment, after the metadata service failure is recovered, the standby metadata service establishing a connection relationship with the client can provide normal service for the client, and the condition that the inode information being used by the client is not loaded in the metadata service cache is not caused. According to the embodiment, when the metadata service fault is recovered, the loading time of the inode information can be shortened, and the efficiency of the metadata service fault recovery is improved.
Referring to fig. 2, fig. 2 is a flowchart of another metadata cluster failure recovery method according to an embodiment of the present disclosure.
The specific steps may include:
s201: and inquiring the inode holding authority of each client, and generating the operation file list according to the inode information corresponding to the inode holding authority as the target inode information.
Wherein the inode holding permission comprises inode opening permission and/or inode modification attribute field permission. When the user end uses some inode information, the corresponding inode holding authority is necessarily available, the inode authority may be an inode opening authority and/or an inode modification attribute field authority, and of course, the inode holding authority may also be other authorities, which is not specifically limited herein. There may be an operation of updating the operation file list according to a preset period, and the inode holding authority is the authority corresponding to the inode information being used by the client at the current time.
S202: when a metadata cluster is detected to be out of order, determining a failure metadata service in the metadata cluster;
s203: inquiring a standby metadata service corresponding to the failure metadata service, and establishing communication connection between all clients and the standby metadata service;
s204: transmitting target inode information in the operation file list of each client to the standby metadata service so that the metadata cluster recovers external services; the target inode information is the inode information used by the client at the current moment.
S205: and uploading prompt information of the failure metadata service downtime.
In this embodiment, the inode information currently used at this time is specifically the inode information corresponding to the inode holding permission held by the client, so that a normal service can be provided for the client, and the condition that the inode information currently used by the client is not loaded in the metadata service cache is not caused.
Referring to fig. 3, fig. 3 is a schematic structural diagram of a metadata cluster failure recovery system according to an embodiment of the present disclosure;
the system may include:
a failure service determination module 100, configured to determine a failed metadata service in a metadata cluster when a metadata cluster failure is detected;
a redundancy module 200, configured to query a backup metadata service corresponding to the failed metadata service, and establish communication connections between all clients and the backup metadata service;
a failure recovery module 300, configured to transmit target inode information in the operation file list of each client to the standby metadata service, so that the metadata cluster recovers an external service; the target inode information is the inode information used by the client at the current moment.
Further, the fault recovery system further includes:
and the list generation module is used for inquiring the inode holding authority of each client and generating the operation file list according to the inode information corresponding to the inode holding authority as the target inode information.
Further, the inode holding permissions include inode opening permissions and/or inode modification attribute field permissions.
Further, the fault recovery system further includes:
and the fault prompting module is used for uploading the prompting information of the failure metadata service downtime.
Since the embodiment of the system part corresponds to the embodiment of the method part, the embodiment of the system part is described with reference to the embodiment of the method part, and is not repeated here.
According to the embodiment, when the metadata service is recovered from a fault, only the inode information used by the client is transmitted to the standby metadata service, so that the content to be loaded by the standby metadata service is reduced, the time for recovering the fault of the metadata service is shortened, and the metadata cluster can rapidly provide the service to the outside. Further, since the inode information being used in the client is transmitted to the standby metadata service in the embodiment, after the metadata service failure is recovered, the standby metadata service establishing a connection relationship with the client can provide normal service for the client, and the condition that the inode information being used by the client is not loaded in the metadata service cache is not caused. According to the embodiment, when the metadata service fault is recovered, the loading time of the inode information can be shortened, and the efficiency of the metadata service fault recovery is improved.
The present application also provides a computer readable storage medium having stored thereon a computer program which, when executed, may implement the steps provided by the above-described embodiments. The storage medium may include: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The application further provides an electronic device, which may include a memory and a processor, where the memory stores a computer program, and the processor may implement the steps provided by the foregoing embodiments when calling the computer program in the memory. Of course, the electronic device may also include various network interfaces, power supplies, and the like.
The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. For the system disclosed by the embodiment, the description is relatively simple because the system corresponds to the method disclosed by the embodiment, and the relevant points can be referred to the method part for description. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
It is further noted that, in the present specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, 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. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Claims (8)
1. A method of failure recovery for a metadata cluster, comprising:
when a metadata cluster is detected to be out of order, determining a failure metadata service in the metadata cluster;
inquiring a standby metadata service corresponding to the failure metadata service, and establishing communication connection between all clients and the standby metadata service;
transmitting target inode information in the operation file list of each client to the standby metadata service so that the metadata cluster recovers external services; the target inode information is the inode information used by the client at the current moment;
wherein, still include:
and inquiring the inode holding authority of each client, and generating the operation file list according to the inode information corresponding to the inode holding authority as the target inode information.
2. The method of claim 1, wherein the inode holding permissions comprise inode open permissions and/or inode modify attribute field permissions.
3. The method of claim 1, wherein after the metadata cluster recovers the external service, the method further comprises:
and uploading prompt information of the failure metadata service downtime.
4. A system for failover of a metadata cluster, comprising:
the metadata cluster failure detection module is used for detecting the failure of a metadata cluster, and determining the failure metadata service in the metadata cluster;
the redundancy module is used for inquiring the standby metadata service corresponding to the failure metadata service and establishing communication connection between all the clients and the standby metadata service;
the failure recovery module is used for transmitting target inode information in the operation file list of each client to the standby metadata service so that the metadata cluster can recover external services; the target inode information is the inode information used by the client at the current moment;
and the list generation module is used for inquiring the inode holding authority of each client and generating the operation file list according to the inode information corresponding to the inode holding authority as the target inode information.
5. The system of claim 4, wherein the inode holding permissions include inode open permissions and/or inode modify attribute field permissions.
6. The fault recovery system of claim 4, further comprising:
and the fault prompting module is used for uploading the prompting information of the failure metadata service downtime.
7. An electronic device, comprising:
a memory for storing a computer program;
a processor for implementing the steps of a method of failure recovery of a metadata cluster according to any of claims 1 to 3 when executing said computer program.
8. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the method for failure recovery of a metadata cluster according to any one of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810934272.7A CN109165112B (en) | 2018-08-16 | 2018-08-16 | Fault recovery method, system and related components of metadata cluster |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810934272.7A CN109165112B (en) | 2018-08-16 | 2018-08-16 | Fault recovery method, system and related components of metadata cluster |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109165112A CN109165112A (en) | 2019-01-08 |
| CN109165112B true CN109165112B (en) | 2022-02-18 |
Family
ID=64895954
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810934272.7A Active CN109165112B (en) | 2018-08-16 | 2018-08-16 | Fault recovery method, system and related components of metadata cluster |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109165112B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111159786B (en) * | 2019-12-29 | 2022-04-22 | 浪潮电子信息产业股份有限公司 | Metadata protection method and device, electronic equipment and storage medium |
| CN111176898A (en) * | 2019-12-29 | 2020-05-19 | 浪潮电子信息产业股份有限公司 | Distributed file system MDS (maintenance description Server) fault switching method, device, equipment and medium |
| CN111984592B (en) * | 2020-08-28 | 2022-07-19 | 苏州浪潮智能科技有限公司 | Method and system for delayed synchronous recovery of metadata operation authority information |
| CN111984474B (en) * | 2020-09-27 | 2022-08-19 | 苏州浪潮智能科技有限公司 | Method, system and equipment for recovering double-control cluster fault |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101567805A (en) * | 2009-05-22 | 2009-10-28 | 清华大学 | Method for recovering failed parallel file system |
| CN103179185A (en) * | 2012-12-25 | 2013-06-26 | 中国科学院计算技术研究所 | Method and system for creating files in cache of distributed file system client |
| CN106469087A (en) * | 2015-08-19 | 2017-03-01 | 阿里巴巴集团控股有限公司 | Metadata output intent, client and meta data server |
| CN106789180A (en) * | 2016-11-30 | 2017-05-31 | 郑州云海信息技术有限公司 | The service control method and device of a kind of meta data server |
| CN107729178A (en) * | 2017-09-28 | 2018-02-23 | 郑州云海信息技术有限公司 | A kind of Metadata Service process takes over method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9170892B2 (en) * | 2010-04-19 | 2015-10-27 | Microsoft Technology Licensing, Llc | Server failure recovery |
-
2018
- 2018-08-16 CN CN201810934272.7A patent/CN109165112B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101567805A (en) * | 2009-05-22 | 2009-10-28 | 清华大学 | Method for recovering failed parallel file system |
| CN103179185A (en) * | 2012-12-25 | 2013-06-26 | 中国科学院计算技术研究所 | Method and system for creating files in cache of distributed file system client |
| CN106469087A (en) * | 2015-08-19 | 2017-03-01 | 阿里巴巴集团控股有限公司 | Metadata output intent, client and meta data server |
| CN106789180A (en) * | 2016-11-30 | 2017-05-31 | 郑州云海信息技术有限公司 | The service control method and device of a kind of meta data server |
| CN107729178A (en) * | 2017-09-28 | 2018-02-23 | 郑州云海信息技术有限公司 | A kind of Metadata Service process takes over method and device |
Non-Patent Citations (1)
| Title |
|---|
| Lustre文件系统元数据服务恢复机制的改进;钱迎进等;《计算机科学》;20150930;第42卷(第09期);第1-6页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109165112A (en) | 2019-01-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109165112B (en) | Fault recovery method, system and related components of metadata cluster | |
| US9720620B1 (en) | Efficient data volume replication for block-based storage | |
| CN101562543B (en) | Cache data processing method and processing system and device thereof | |
| CN107528872B (en) | Data recovery method and device and cloud storage system | |
| US20190220361A1 (en) | Monitoring Containers In A Distributed Computing System | |
| CN106708653B (en) | Mixed tax big data security protection method based on erasure code and multiple copies | |
| US20120259912A1 (en) | Cluster unique identifier | |
| CN108829787B (en) | Metadata distributed system | |
| CN112130758B (en) | Data reading request processing method and system, electronic equipment and storage medium | |
| CN105511987A (en) | Distributed task management system with high consistency and availability | |
| US20180121531A1 (en) | Data Updating Method, Device, and Related System | |
| CN105069152A (en) | Data processing method and apparatus | |
| CN104486438A (en) | Disaster-tolerant method and disaster-tolerant device of distributed storage system | |
| CN111240892A (en) | Data backup method and device | |
| US8719622B2 (en) | Recording and preventing crash in an appliance | |
| CN112380067A (en) | Metadata-based big data backup system and method under Hadoop environment | |
| CN113687790A (en) | Data reconstruction method, device, equipment and storage medium | |
| CN110888847A (en) | Recycle bin system and file recycling method | |
| CN105471616A (en) | Cache system management method and system | |
| CN112650629B (en) | Block chain index data recovery method, device, equipment and computer storage medium | |
| EP3349416B1 (en) | Relationship chain processing method and system, and storage medium | |
| WO2017080362A1 (en) | Data managing method and device | |
| CN109669642B (en) | Node joining method, system and device of storage system and readable storage medium | |
| CN107908370B (en) | Data storage method and device | |
| US20240244414A1 (en) | Session binding relationship processing method and apparatus, electronic device, and readable 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |