CN109165112A - A kind of fault recovery method, system and the associated component of metadata cluster - Google Patents
A kind of fault recovery method, system and the associated component of metadata cluster Download PDFInfo
- Publication number
- CN109165112A CN109165112A CN201810934272.7A CN201810934272A CN109165112A CN 109165112 A CN109165112 A CN 109165112A CN 201810934272 A CN201810934272 A CN 201810934272A CN 109165112 A CN109165112 A CN 109165112A
- Authority
- CN
- China
- Prior art keywords
- metadata
- inode
- fault
- service
- metadata service
- 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.)
- Granted
Links
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
Abstract
This application discloses a kind of fault recovery method of metadata cluster, the fault recovery method includes determining the fault metadata service in the metadata cluster when detecting that metadata cluster breaks down；Spare Metadata Service corresponding with fault metadata service is inquired, and establishes the communication connection between all clients and spare Metadata Service；Target inode information in the operation file list of each client is transmitted to the spare Metadata Service, so that metadata cluster recovery externally services；Wherein, target inode information is client inode information currently in use described in current time.This method can reduce the load time of inode information in Metadata Service fault recovery, improve the efficiency of Metadata Service fault recovery.Disclosed herein as well is a kind of fault recovery system of metadata cluster, a kind of computer readable storage medium and a kind of electronic equipment, have the above beneficial effect.
Description
Technical field
The present invention relates to data storage management field, in particular to a kind of fault recovery method of metadata cluster, system,
A kind of computer readable storage medium and a kind of electronic equipment.
Background technique
When metadata cluster breaks down, spare Metadata Service takes over the Metadata Service of failure, restores cluster
Externally service.Restoring this period, the Metadata Service taken over does not provide service externally, that is, is not responding to client request.
Therefore recovery time length directly influences user experience.
In the prior art, it needs to re-establish connection, all clients with client during the fault recovery of metadata cluster
Inode (index node) information all in existing caching can all be issued spare Metadata Service, so as to spare metadata clothes
Business is all loaded into these inode information in memory.But the inode information content in the existing caching of client is huge, if
All load certainly will increase failure recovery time to metadata.
Therefore, how in Metadata Service fault recovery, the load time of inode information is reduced, improves metadata clothes
The efficiency of business fault recovery is a technical problem that technical personnel in the field need to solve at present.
Summary of the invention
The purpose of the application is to provide the fault recovery method of metadata cluster a kind of, system, a kind of computer-readable deposits
Storage media and a kind of electronic equipment can reduce the load time of inode information in Metadata Service fault recovery, improve
The efficiency of Metadata Service fault recovery.
In order to solve the above technical problems, the application provides a kind of fault recovery method of metadata cluster, the fault recovery
Method includes:
When detecting that metadata cluster breaks down, the fault metadata service in the metadata cluster is determined；
Inquire corresponding with fault metadata service spare Metadata Service, and establish all clients with it is described standby
With the communication connection between Metadata Service；
Target inode information in the operation file list of each client is transmitted to the spare metadata clothes
Business, so that the metadata cluster recovery externally services；Wherein, the target inode information is client described in current time
Inode information currently in use.
Optionally, further includes:
The inode for inquiring each client holds permission, and corresponding according to permission is held with the inode
Inode information generates the operation file list as the target inode information.
Optionally, it includes that inode opens permission and/or inode modification attribute field permission that the inode, which holds permission,.
Optionally, after the metadata cluster recovery externally services, further includes:
Upload the prompt information of the fault metadata service delay machine.
Present invention also provides a kind of fault recovery system of metadata cluster, which includes:
Failed services determining module, for determining the metadata cluster when detecting that metadata cluster breaks down
In fault metadata service；
Redundant module for inquiring spare Metadata Service corresponding with fault metadata service, and is established all
Communication connection between client and the spare Metadata Service；
Failure Recovery Module, for transmitting the target inode information in the operation file list of each client
To the spare Metadata Service, so that the metadata cluster recovery externally services；Wherein, the target inode information is
The inode information currently in use of client described in current time.
Optionally, further includes:
List Generating Module, the inode for inquiring each client hold permission, and according to the inode
Hold the corresponding inode information of permission as the target inode information and generates the operation file list.
Optionally, it includes that inode opens permission and/or inode modification attribute field permission that the inode, which holds permission,.
Optionally, further includes:
Fault cues module, for uploading the prompt information of fault metadata service delay machine.
Present invention also provides a kind of computer readable storage mediums, are stored thereon with computer program, the computer
Program realizes the step of fault recovery method of above-mentioned metadata cluster executes when executing.
Present invention also provides a kind of electronic equipment, including memory and processor, calculating is stored in the memory
Machine program, the processor realize the fault recovery side of above-mentioned metadata cluster when calling the computer program in the memory
The step of method executes.
The present invention provides a kind of fault recovery methods of metadata cluster, including work as and detect that event occurs in metadata cluster
When barrier, the fault metadata service in the metadata cluster is determined；It inquires corresponding spare with fault metadata service
Metadata Service, and establish the communication connection between all clients and the spare Metadata Service；By each client
Target inode information in the operation file list at end is transmitted to the spare Metadata Service, so as to the metadata cluster
Restore externally service；Wherein, the target inode information is client inode information currently in use described in current time.
The application is by being only transmitted to client inode information currently in use when restoring Metadata Service failure
In spare Metadata Service, reducing spare Metadata Service needs content to be loaded, shortens Metadata Service fault recovery
Time, metadata set group can be made quickly externally to provide service.Further, since the application will make in client
Inode information is transmitted in spare Metadata Service, therefore after Metadata Service fault recovery, is established and is connected with client
The spare Metadata Service for connecing relationship can provide normal service for client, not will cause client inode currently in use
Information is not loaded into the situation in Metadata Service caching.The application can be reduced in Metadata Service fault recovery
The load time of inode information improves the efficiency of Metadata Service fault recovery.The application additionally provides a kind of metadata simultaneously
The fault recovery system of cluster, a kind of computer readable storage medium and a kind of electronic equipment have above-mentioned beneficial effect, herein
It repeats no more.
Detailed description of the invention
In ord to more clearly illustrate embodiments of the present application, attached drawing needed in the embodiment will be done simply below
It introduces, it should be apparent that, the drawings in the following description are only some examples of the present application, for ordinary skill people
For member, without creative efforts, it is also possible to obtain other drawings based on these drawings.
Fig. 1 is a kind of flow chart of the fault recovery method of metadata cluster provided by the embodiment of the present application；
Fig. 2 is the flow chart of the fault recovery method of another kind metadata cluster provided by the embodiment of the present application；
Fig. 3 is a kind of structural schematic diagram of the fault recovery system of metadata cluster provided by the embodiment of the present application.
Specific embodiment
To keep the purposes, technical schemes and advantages of the embodiment of the present application clearer, below in conjunction with the embodiment of the present application
In attached drawing, the technical scheme in the embodiment of the application is clearly and completely described, it is clear that described embodiment is
Some embodiments of the present application, instead of all the embodiments.Based on the embodiment in the application, those of ordinary skill in the art
Every other embodiment obtained without making creative work, shall fall in the protection scope of this application.
Below referring to Figure 1, Fig. 1 is a kind of fault recovery method of metadata cluster provided by the embodiment of the present application
Flow chart.
Specific steps may include:
S101: when detecting that metadata cluster breaks down, the fault metadata clothes in the metadata cluster are determined
Business；
Wherein, the present embodiment is how to realize the implementation of fast failure recovery for when metadata cluster breaks down
Mode.It may include multiple Metadata Services in metadata cluster, both may include that service interaction is occurring with client
Metadata Service may include spare redundancy Metadata Service；Metadata Service can be understood as a process.Due to first number
According in cluster, there are multiple Metadata Services, therefore after metadata cluster breaks down, which the determination first of this step is
There is failure in Metadata Service, i.e., the fault metadata service in determination metadata set group in this step, herein and unlimited
Determine the quantity of fault metadata service.It should be noted that the present embodiment will only break down, preceding and client carries out business friendship
Mutually and there is fault metadata service as fault metadata service.
S102: corresponding with the fault metadata service spare Metadata Service of inquiry, and establish all clients and
Communication connection between the spare Metadata Service；
Wherein, the present embodiment, which can be spare Metadata Service, can be used to substitute metadata currently in use clothes used
Business, is also possible to there are the corresponding relationship of certain Metadata Services currently in use and spare Metadata Service, right according to this
Answer relational query spare Metadata Service corresponding with fault metadata service.In short, being determined to take over failure member
After the spare Metadata Service of data service, it can be built with spare Metadata Service with the corresponding all clients of metadata cluster
Vertical communication connection, so that all clients transmit necessary inode information to spare Metadata Service.
S103: the target inode information in the operation file list of each client is transmitted to the spare member
Data service, so that the metadata cluster recovery externally services；Wherein, the target inode information is described in current time
Client inode information currently in use.
Wherein, since there is no the inode information in client-cache in the memory of spare Metadata Service, it is therefore desirable to
Inode information in client is transmitted to spare Metadata Service.It is by all inode information of client in the prior art
It is all transmitted to spare Metadata Service, but since whole inode information data amounts is larger, will affect the effect of fault recovery
Rate.The present embodiment is specifically to work as spare Metadata Service in the inode information transmission currently in use of current time client
At the time of the preceding moment can refer to that client and spare Metadata Service establish communication connection.
It should be noted that it is currently in use to be stored with client described in current time in the operation file list of client
Inode information, and target inode information is set by inode information currently in use.
The present embodiment is by only transmitting client inode information currently in use when restoring Metadata Service failure
Content to be loaded is needed to spare Metadata Service in spare Metadata Service, is reduced, it is extensive to shorten Metadata Service failure
The multiple time can make metadata set group quickly externally provide service.Further, due to the present embodiment by client just
It is transmitted in spare Metadata Service in the inode information used, therefore after Metadata Service fault recovery, is built with client
The spare Metadata Service of vertical connection relationship can provide normal service for client, and it is currently in use not will cause client
Inode information is not loaded into the situation in Metadata Service caching.The present embodiment can in Metadata Service fault recovery,
The load time of inode information is reduced, the efficiency of Metadata Service fault recovery is improved.
Fig. 2 is referred to below, and Fig. 2 is the fault recovery method of another kind metadata cluster provided by the embodiment of the present application
Flow chart.
Specific steps may include:
S201: the inode of each client of inquiry holds permission, and corresponding according to permission is held with the inode
Inode information generate the operation file list as the target inode information.
Wherein, it includes that inode opens permission and/or inode modification attribute field permission that the inode, which holds permission,.When
It when certain inode information are used in user terminal, necessarily have corresponding inode and holds permission, which can be
Inode opens permission and/or inode modifies attribute field permission, and certain inode, which holds permission, can also be other permissions,
Herein without specifically limiting.There may be the operation for updating operation file list according to predetermined period, inode holds permission
It is exactly the corresponding permission of current time client inode information currently in use.
S202: when detecting that metadata cluster breaks down, the fault metadata clothes in the metadata cluster are determined
Business；
S203: corresponding with the fault metadata service spare Metadata Service of inquiry, and establish all clients and
Communication connection between the spare Metadata Service；
S204: the target inode information in the operation file list of each client is transmitted to the spare member
Data service, so that the metadata cluster recovery externally services；Wherein, the target inode information is described in current time
Client inode information currently in use.
S205: the prompt information of the fault metadata service delay machine is uploaded.
Current time inode information currently in use is specially that client holds inode and holds permission pair by the present embodiment
The inode information answered can provide normal service for client, and not will cause client inode information currently in use does not have
Situation about being loaded into Metadata Service caching.
Fig. 3 is referred to, Fig. 3 is a kind of structure of the fault recovery system of metadata cluster provided by the embodiment of the present application
Schematic diagram；
The system may include:
Failed services determining module 100, for determining the metadata set when detecting that metadata cluster breaks down
Fault metadata service in group；
Redundant module 200 for inquiring spare Metadata Service corresponding with fault metadata service, and establishes institute
There is the communication connection between client and the spare Metadata Service；
Failure Recovery Module 300, for passing the target inode information in the operation file list of each client
The spare Metadata Service is transported to, so that the metadata cluster recovery externally services；Wherein, the target inode information
For the inode information currently in use of client described in current time.
Further, the fault recovery system further include:
List Generating Module, the inode for inquiring each client hold permission, and according to the inode
Hold the corresponding inode information of permission as the target inode information and generates the operation file list.
Further, it includes that inode opens permission and/or inode modification attribute field power that the inode, which holds permission,
Limit.
Further, the fault recovery system further include:
Fault cues module, for uploading the prompt information of fault metadata service delay machine.
Since the embodiment of components of system as directed is corresponded to each other with the embodiment of method part, the embodiment of components of system as directed is asked
Referring to the description of the embodiment of method part, wouldn't repeat here.
The present embodiment is by only transmitting client inode information currently in use when restoring Metadata Service failure
Content to be loaded is needed to spare Metadata Service in spare Metadata Service, is reduced, it is extensive to shorten Metadata Service failure
The multiple time can make metadata set group quickly externally provide service.Further, due to the present embodiment by client just
It is transmitted in spare Metadata Service in the inode information used, therefore after Metadata Service fault recovery, is built with client
The spare Metadata Service of vertical connection relationship can provide normal service for client, and it is currently in use not will cause client
Inode information is not loaded into the situation in Metadata Service caching.The present embodiment can in Metadata Service fault recovery,
The load time of inode information is reduced, the efficiency of Metadata Service fault recovery is improved.
Present invention also provides a kind of computer readable storage mediums, have computer program thereon, the computer program
It is performed and step provided by above-described embodiment may be implemented.The storage medium may include: USB flash disk, mobile hard disk, read-only deposit
Reservoir (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or
The various media that can store program code such as CD.
Present invention also provides a kind of electronic equipment, may include memory and processor, have meter in the memory
Calculation machine program may be implemented provided by above-described embodiment when the processor calls the computer program in the memory
Step.Certain electronic equipment can also include various network interfaces, the components such as power supply.
Each embodiment is described in a progressive manner in specification, the highlights of each of the examples are with other realities
The difference of example is applied, the same or similar parts in each embodiment may refer to each other.For system disclosed in embodiment
Speech, since it is corresponded to the methods disclosed in the examples, so being described relatively simple, related place is referring to method part illustration
?.It should be pointed out that for those skilled in the art, under the premise of not departing from the application principle, also
Can to the application, some improvement and modification can also be carried out, these improvement and modification also fall into the protection scope of the claim of this application
It is interior.
It should also be noted that, in the present specification, relational terms such as first and second and the like be used merely to by
One entity or operation are distinguished with another entity or operation, without necessarily requiring or implying these entities or operation
Between there are any actual relationship or orders.Moreover, the terms "include", "comprise" or its any other variant meaning
Covering non-exclusive inclusion, so that the process, method, article or equipment for including a series of elements not only includes that
A little elements, but also including other elements that are not explicitly listed, or further include for this process, method, article or
The intrinsic element of equipment.Under the situation not limited more, the element limited by sentence "including a ..." is not arranged
Except there is also other identical elements in the process, method, article or apparatus that includes the element.
Claims (10)
1. a kind of fault recovery method of metadata cluster characterized by comprising
When detecting that metadata cluster breaks down, the fault metadata service in the metadata cluster is determined；
Spare Metadata Service corresponding with fault metadata service is inquired, and establishes all clients and the spare member
Communication connection between data service；
Target inode information in the operation file list of each client is transmitted to the spare Metadata Service,
So that the metadata cluster recovery externally services；Wherein, the target inode information be current time described in client
The inode information used.
2. fault recovery method according to claim 1, which is characterized in that further include:
The inode for inquiring each client holds permission, and believes according to the corresponding inode of permission is held with the inode
Breath generates the operation file list as the target inode information.
3. fault recovery method according to claim 2, which is characterized in that it includes that inode is opened that the inode, which holds permission,
Permission and/or inode modify attribute field permission.
4. fault recovery method according to claim 1, which is characterized in that externally service it in the metadata cluster recovery
Afterwards, further includes:
Upload the prompt information of the fault metadata service delay machine.
5. a kind of fault recovery system of metadata cluster characterized by comprising
Failed services determining module, for determining in the metadata cluster when detecting that metadata cluster breaks down
Fault metadata service；
Redundant module for inquiring spare Metadata Service corresponding with fault metadata service, and establishes all clients
Communication connection between end and the spare Metadata Service；
Failure Recovery Module, for the target inode information in the operation file list of each client to be transmitted to institute
Spare Metadata Service is stated, so that the metadata cluster recovery externally services；Wherein, the target inode information is current
The inode information currently in use of client described in moment.
6. fault recovery system according to claim 5, which is characterized in that further include:
List Generating Module, the inode for inquiring each client holds permission, and holds according to the inode
The corresponding inode information of permission generates the operation file list as the target inode information.
7. fault recovery system according to claim 6, which is characterized in that it includes that inode is opened that the inode, which holds permission,
Permission and/or inode modify attribute field permission.
8. fault recovery system according to claim 5, which is characterized in that further include:
Fault cues module, for uploading the prompt information of fault metadata service delay machine.
9. a kind of electronic equipment characterized by comprising
Memory, for storing computer program；
Processor is realized when for executing the computer program such as the described in any item metadata clusters of Claims 1-4
The step of fault recovery method.
10. a kind of computer readable storage medium, which is characterized in that be stored with computer on the computer readable storage medium
Program realizes the event such as the described in any item metadata clusters of Claims 1-4 when the computer program is executed by processor
The step of hindering restoration methods.
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 true CN109165112A (en) | 2019-01-08 |
| CN109165112B 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) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111159786A (en) * | 2019-12-29 | 2020-05-15 | 浪潮电子信息产业股份有限公司 | 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 |
| CN111984474A (en) * | 2020-09-27 | 2020-11-24 | 苏州浪潮智能科技有限公司 | Method, system and equipment for recovering double-control cluster fault |
| CN111984592A (en) * | 2020-08-28 | 2020-11-24 | 苏州浪潮智能科技有限公司 | Method and system for delaying synchronous recovery of metadata operation authority information |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101567805A (en) * | 2009-05-22 | 2009-10-28 | 清华大学 | Method for recovering failed parallel file system |
| US20110258488A1 (en) * | 2010-04-19 | 2011-10-20 | Microsoft Corporation | Server Failure Recovery |
| 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 |
-
2018
- 2018-08-16 CN CN201810934272.7A patent/CN109165112B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101567805A (en) * | 2009-05-22 | 2009-10-28 | 清华大学 | Method for recovering failed parallel file system |
| US20110258488A1 (en) * | 2010-04-19 | 2011-10-20 | Microsoft Corporation | Server Failure Recovery |
| 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文件系统元数据服务恢复机制的改进", 《计算机科学》 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111159786A (en) * | 2019-12-29 | 2020-05-15 | 浪潮电子信息产业股份有限公司 | 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 |
| CN111159786B (en) * | 2019-12-29 | 2022-04-22 | 浪潮电子信息产业股份有限公司 | Metadata protection method and device, electronic equipment and storage medium |
| CN111984592A (en) * | 2020-08-28 | 2020-11-24 | 苏州浪潮智能科技有限公司 | Method and system for delaying synchronous recovery of metadata operation authority information |
| CN111984474A (en) * | 2020-09-27 | 2020-11-24 | 苏州浪潮智能科技有限公司 | Method, system and equipment for recovering double-control cluster fault |
| CN111984474B (en) * | 2020-09-27 | 2022-08-19 | 苏州浪潮智能科技有限公司 | Method, system and equipment for recovering double-control cluster fault |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109165112B (en) | 2022-02-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11740826B2 (en) | Policy-based hierarchical data protection in distributed storage | |
| CN109165112A (en) | A kind of fault recovery method, system and the associated component of metadata cluster | |
| CN107193490B (en) | Distributed data storage system and method based on block chain | |
| CN107528872B (en) | Data recovery method and device and cloud storage system | |
| CN106708653B (en) | Mixed tax big data security protection method based on erasure code and multiple copies | |
| CN106534328A (en) | Node connection method and distributed computing system | |
| CN106850710A (en) | A kind of safe data cloud storage system, client terminal, storage server and application process | |
| CN101009516A (en) | A method and system for data synchronization | |
| CN109102273B (en) | Method and system for realizing distributed intelligent payment routing | |
| CN103944981A (en) | Cloud storage system and implement method based on erasure code technological improvement | |
| CN104424287B (en) | Data query method and apparatus | |
| CN111130835A (en) | Data center dual-active system, switching method, device, equipment and medium | |
| CN101557427A (en) | Method for providing diffluent information and realizing the diffluence of clients, system and server thereof | |
| CN102411639A (en) | Multi-copy storage management method and system of metadata | |
| US11442827B2 (en) | Policy-based hierarchical data protection in distributed storage | |
| CN103780417A (en) | Database failure transfer method based on cloud hard disk and device thereof | |
| CN105869057A (en) | Comment storage device, comment reading method and apparatus, and comment writing method and apparatus | |
| CN105554121A (en) | Method and system for realizing load equalization of distributed cache system | |
| CN104579765A (en) | Disaster tolerance method and device for cluster system | |
| CN103823807A (en) | Data de-duplication method, device and system | |
| CN108156040A (en) | A kind of central control node in distribution cloud storage system | |
| CN103516734A (en) | Data processing method, device and system | |
| EP3349416B1 (en) | Relationship chain processing method and system, and storage medium | |
| CN102436468A (en) | Load balancing method and system based on database cluster | |
| CN111427965B (en) | Management method and management system for water affair data |
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 |