CN108776628B - Method, device and medium for avoiding crash during CTDB data recovery - Google Patents
Method, device and medium for avoiding crash during CTDB data recovery Download PDFInfo
- Publication number
- CN108776628B CN108776628B CN201810529591.XA CN201810529591A CN108776628B CN 108776628 B CN108776628 B CN 108776628B CN 201810529591 A CN201810529591 A CN 201810529591A CN 108776628 B CN108776628 B CN 108776628B
- Authority
- CN
- China
- Prior art keywords
- task
- recovery
- memory space
- target
- data
- 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
- 238000011084 recovery Methods 0.000 title claims abstract description 166
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000013507 mapping Methods 0.000 claims abstract description 66
- 230000002159 abnormal effect Effects 0.000 claims abstract description 38
- 230000006870 function Effects 0.000 claims abstract description 32
- 238000004590 computer program Methods 0.000 claims description 9
- 230000009286 beneficial effect Effects 0.000 abstract description 2
- 238000012544 monitoring process Methods 0.000 description 7
- 230000009471 action Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 241001362551 Samba Species 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 1
- 238000012545 processing Methods 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/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1464—Management of the backup or restore process for networked environments
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
- G06F9/5016—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals the resource being the memory
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Hardware Redundancy (AREA)
Abstract
The invention discloses a method, a device and a medium for avoiding crash during CTDB data recovery, wherein the method comprises the following steps: when the CTDB main node executes a data recovery task, acquiring the current state of a target recovery task corresponding to a target task ID; when the current state is abnormal, searching a mapping linked list corresponding to the target task ID in a task list; the mapping chain table comprises a data recovery function for executing a target recovery task and a pre-applied memory space address for caching recovery data, and the data recovery function and the memory space address have a mapping relation; and removing the mapping linked list from the task list so as to avoid the crash of the main node of the CTDB caused by accessing the memory space address. The method ensures the reliability of the CTDB during data recovery. In addition, the invention also provides a data recovery device and medium of the CTDB, and the beneficial effects are the same as the above.
Description
Technical Field
The present invention relates to the field of databases, and in particular, to a method, an apparatus, and a medium for avoiding crash of CTDB data during recovery.
Background
The Samba service is software for realizing an SMB protocol on a Linux or Unix system, and can realize the access of a client to data in a server.
The Samba service stores user data and work records used or generated at runtime into a CTDB (temporary database cluster), which is often installed in a plurality of device nodes in a cluster environment, wherein the CTDB data nodes are used for controlling data access of different TDBs (temporary databases), and the CTDB master node is used for monitoring and controlling the CTDB data nodes. When a CTDB master node fails or changes, it is often necessary to restore its records to the TDB integrity. The relevant parameters required for data recovery are often registered in the task list.
As shown in fig. 1, the structure of the task List referred to for data recovery in the current situation is shown, where srvid _ handler _ List is the task List; srvid is a task ID (identity number); srvid _ handler h is a mapping chain table for recording the corresponding relationship between a data recovery function (pull _ database _ handler) and a pre-applied memory space address (vent _ req), and a unique corresponding relationship exists between a task ID and the mapping chain table. When data recovery is carried out, the CTDB main node searches a corresponding mapping linked list according to the task ID according to the structure of the task list, obtains a corresponding recovery function and a memory space address according to the mapping linked list, and further executes the recovery function to cache the obtained data to the memory space address.
However, since the CTDB data node may still perform IO operations on the data in the TDB during the recovery process, a data recovery error may occur. In this case, the CTDB master node may release the memory space for caching and recovering data under the memory space address (vent _ req), and when the system tries data recovery again or performs relevant monitoring on a data recovery task, a core file may be generated due to the fact that the memory space cannot be found through the memory space address, which may cause a crash of the CTDB master node, and it is difficult to ensure reliability of data recovery performed by the CTDB.
Therefore, it is a problem to be solved by those skilled in the art to provide a method for avoiding a crash of CTDB data recovery to ensure the reliability of CTDB data recovery.
Disclosure of Invention
The invention aims to provide a method, a device and a medium for avoiding crash of CTDB data during recovery so as to ensure the reliability of the CTDB during data recovery.
To solve the above technical problem, the present invention provides a method for avoiding crash of CTDB data during recovery, comprising:
when the CTDB main node executes a data recovery task, acquiring the current state of a target recovery task corresponding to a target task ID;
when the current state is abnormal, searching a mapping linked list corresponding to the target task ID in a task list; the mapping chain table comprises a data recovery function for executing a target recovery task and a pre-applied memory space address for caching recovery data, and the data recovery function and the memory space address have a mapping relation;
and removing the mapping linked list from the task list so as to avoid the crash of the main node of the CTDB caused by accessing the memory space address.
Preferably, when the current state is abnormal, the method further comprises:
recording related information of the target recovery task to a task log representing uncompleted tasks; the related information at least includes memory space capacity corresponding to the memory space address and a data recovery function.
Preferably, after recording the relevant information of the target recovery task to the task log representing the uncompleted task, the method further comprises:
applying for a new memory space address in the CTDB main node according to the memory space capacity, establishing a mapping relation between the new memory space address and a data recovery function, and generating a new mapping linked list;
and correspondingly recording the new mapping linked list and the new target task ID to the task list so as to execute the target recovery task again.
Preferably, the obtaining of the current state of the target recovery task corresponding to the target task ID specifically includes:
and acquiring the current state corresponding to the target task ID in a random mode.
Preferably, the target task ID is specifically a random number in hexadecimal form.
Preferably, the CTDB master node is a server running a Linux operating system.
In addition, the invention also provides a device for avoiding the crash of CTDB data recovery, which comprises:
the state acquisition module is used for acquiring the current state of a target recovery task corresponding to the target task ID when the CTDB main node executes a data recovery task;
the linked list searching module is used for searching a mapping linked list corresponding to the target task ID in the task list when the current state is abnormal; the mapping chain table comprises a data recovery function for executing a target recovery task and a pre-applied memory space address for caching recovery data, and the data recovery function and the memory space address have a mapping relation;
and the linked list removing module is used for removing the mapping linked list from the task list so as to avoid the main node of the CTDB from being crashed due to the access to the memory space address.
Preferably, the apparatus further comprises:
the log recording module is used for recording the related information of the target recovery task to a task log representing an uncompleted task; the related information at least includes memory space capacity corresponding to the memory space address and a data recovery function.
In addition, the invention also provides a device for avoiding the crash of CTDB data recovery, which comprises:
a memory for storing a computer program;
a processor for implementing the steps of the method for avoiding crash of CTDB data recovery as described above when executing a computer program.
Furthermore, the present invention also provides a computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the steps of the method for avoiding a crash upon recovery of CTDB data as described above.
According to the method for avoiding the crash of the CTDB data recovery, when the data recovery of the CTDB main node is abnormal, the corresponding mapping linked list is searched in the task list according to the task ID of the abnormal task, and the mapping linked list is removed from the task list. Because the mapping linked list contains the memory space address applied in advance, even if the system releases the memory space address due to the abnormal data recovery, the system can also ensure that the system can not obtain the internal slave space address in the task list when trying to execute the abnormal task again or perform the related monitoring of the abnormal task, thereby avoiding the core file generated by the system due to the fact that the memory space can not be found, further avoiding the crash of the CTDB and ensuring the reliability of the CTDB during data recovery. In addition, the invention also provides a device and a medium for avoiding the crash of CTDB data during recovery, and the beneficial effects are the same as the above.
Drawings
In order to illustrate the embodiments of the present invention more clearly, the drawings that are needed in 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 invention, and that other drawings can be obtained by those skilled in the art without inventive effort.
Fig. 1 is a structure of a task list referred to for data recovery in the present case;
fig. 2 is a flowchart of a method for avoiding crash during CTDB data recovery according to an embodiment of the present invention;
fig. 3 is a block diagram of an apparatus for avoiding crash during CTDB data recovery according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without any creative work belong to the protection scope of the present invention.
The core of the invention is to provide a method for avoiding the crash of the CTDB data during the recovery, so as to ensure the reliability of the CTDB during the data recovery. Another core of the present invention is to provide an apparatus and medium for preventing crash of CTDB data during recovery.
In order that those skilled in the art will better understand the disclosure, the invention will be described in further detail with reference to the accompanying drawings and specific embodiments.
Example one
Fig. 2 is a flowchart of a method for avoiding crash during CTDB data recovery according to an embodiment of the present invention. Referring to fig. 2, the method for avoiding the crash of the CTDB data during the recovery includes the following specific steps:
step S10: and when the CTDB main node executes the data recovery task, acquiring the current state of the target recovery task corresponding to the target task ID.
It should be noted that the CTDB data node often manages a plurality of TDB databases, and when the CTDB master node executes a data recovery task, the data recovery task is executed in units of the TDB databases, that is, a corresponding data recovery task is established for each TDB database, where the data recovery task is used to pull data in the TDB database and rebuild the data into the CTDB node, and correspondingly, each data recovery task has a corresponding task ID. In addition, data interaction between the CTDB master node and the CTDB data node is a technical content known in the art, and is not described herein. In this step, the current state of the target recovery task corresponding to the target ID is obtained by selecting the target task ID, and since the TDB database may not be "frozen" when the TDB database is pulled for data recovery, the TDB database still has data IO, which causes data inconsistency, and further, the current state may be abnormal.
Step S11: and when the current state is abnormal, searching a mapping linked list corresponding to the target task ID in the task list.
The mapping chain table comprises a data recovery function for executing the target recovery task and a pre-applied memory space address for caching recovery data, and the data recovery function and the memory space address have a mapping relation.
Referring to fig. 1, a task List (srvid _ handler _ List) includes a series of data recovery tasks, each data recovery task has a corresponding task ID (srvid), and the task ID and a corresponding mapping linked List (srvid _ handler) have a corresponding relationship, that is, each task ID has only one corresponding mapping linked List, a data recovery function (pull _ database _ handler) and a memory space address (recent _ req) are correspondingly recorded in the mapping linked List, and when a CTDB node executes a data recovery task, a target mapping linked List is obtained according to the target task ID, a recovery function recorded in the target mapping linked List is called, and a result generated by the recovery function is cached in a memory block under the memory space address.
Step S12: and removing the mapping linked list from the task list so as to avoid the crash of the main node of the CTDB caused by accessing the memory space address.
When the execution of the data recovery task is abnormal, the memory space corresponding to the memory space address in the mapping linked list is released, and then the memory block for caching data cannot be found according to the memory space address, so that once the memory space address is accessed due to the fact that the data recovery task is executed again or the data recovery task is monitored in a related mode, the occurrence of memory empty access is caused, and the main node of the CTDB is broken down. In the step, the mapping linked list is removed from the task list, so that the mapping linked list is prevented from being searched in the task list, and the condition that the memory space address is searched is further prevented.
According to the method for avoiding the crash of the CTDB data recovery, when the data recovery of the CTDB main node is abnormal, the corresponding mapping linked list is searched in the task list according to the task ID of the abnormal task, and the mapping linked list is removed from the task list. Because the mapping linked list contains the memory space address applied in advance, even if the system releases the memory space address due to the abnormal data recovery, the system can also ensure that the system can not obtain the internal slave space address in the task list when trying to execute the abnormal task again or perform the related monitoring of the abnormal task, thereby avoiding the core file generated by the system due to the fact that the memory space can not be found, further avoiding the crash of the CTDB and ensuring the reliability of the CTDB during data recovery.
Example two
On the basis of the above examples, the present invention also provides a series of preferred embodiments as follows.
As a preferred embodiment, when the current state is abnormal, the method further comprises:
and recording the related information of the target recovery task to a task log representing the uncompleted task.
The related information at least includes memory space capacity corresponding to the memory space address and a data recovery function.
Considering that the total amount of data recovery tasks executed by the CTDB master node is often large, when a data recovery task is abnormal, data in the TDB database may not be smoothly reconstructed to the CTDB master node, which is incomplete for the overall data recovery of the CTDB master node, so that the related information of an incomplete target recovery task is recorded in the form of a task log in the present embodiment, which is convenient for a technician to perform corresponding processing on the incomplete target recovery task according to the content recorded by the task log. Since sufficient memory space capacity and correct data recovery function are the basis for ensuring that data recovery is completed, in the present embodiment, the related information at least includes the memory space capacity corresponding to the memory space address and the data recovery function, so as to recover the data that is not successfully recovered again.
On the basis of the foregoing embodiment, as a preferred embodiment, after recording the relevant information of the target recovery task to the task log representing the uncompleted task, the method further includes:
applying for a new memory space address in the CTDB main node according to the memory space capacity, establishing a mapping relation between the new memory space address and a data recovery function, and generating a new mapping linked list;
and correspondingly recording the new mapping linked list and the new target task ID to the task list so as to execute the target recovery task again.
It can be understood that, in the embodiment, a new memory space address is applied according to the memory space capacity recorded in the task log, the new memory space address and the data recovery function are mapped into a new mapping linked list, and the mapping linked list and the new target task ID are correspondingly recorded in the task list, so that the CTDB master node executes the target recovery task again according to the new target task ID in the task list, and thus the integrity of data recovery of the CTDB master node is ensured.
In addition, as a preferred embodiment, the obtaining of the current state of the target recovery task corresponding to the target task ID specifically includes:
and acquiring the current state corresponding to the target task ID in a random mode.
In the task list, the task IDs of the data recovery tasks are arranged in sequence, so that the randomness of the selected target recovery task is improved, and the current state of each data recovery task can be relatively fairly known.
Further, as a preferred embodiment, the target task ID is specifically a random number in hexadecimal form.
In consideration of the fact that the number of the TDB databases managed by the CTDB master node is relatively large under the current condition, and each TDB database corresponds to one data recovery task, the whole number of the data recovery tasks is also relatively large, the random number is used as the task ID, the repeated situation among the task IDs can be avoided, and the hexadecimal number represents the task ID and can relatively reduce the occupation of the space of the digits due to the fact that the hexadecimal number represents the value of each digit.
Furthermore, as a preferred embodiment, the CTDB master node is embodied as a server running a Linux operating system.
The Linux operating system is an open source operating system, so that the use cost is relatively saved, and the bottom layer codes of the Linux operating system are visible, so that the Linux operating system is easier to maintain, and has higher stability and higher safety compared with a Windows system, and the working reliability of the CTDB node is ensured.
EXAMPLE III
In the above, the detailed description is given to the embodiment of the method for avoiding the crash during the recovery of the CTDB data, and the present invention further provides a device for avoiding the crash during the recovery of the CTDB data corresponding to the method.
Fig. 3 is a block diagram of an apparatus for avoiding crash during CTDB data recovery according to an embodiment of the present invention. The device for avoiding the crash of the CTDB data during recovery provided by the embodiment of the invention comprises the following components:
the state obtaining module 10 is configured to obtain a current state of the target recovery task corresponding to the target task ID when the CTDB master node executes the data recovery task.
A linked list searching module 11, configured to search, when the current state is abnormal, a mapping linked list corresponding to the target task ID in the task list; the mapping chain table comprises a data recovery function for executing the target recovery task and a pre-applied memory space address for caching recovery data, and the data recovery function and the memory space address have a mapping relation.
The linked list removing module 12 is configured to remove the mapping linked list from the task list, so as to avoid a crash of the CTDB master node due to access to the memory space address.
According to the device for avoiding the crash of the CTDB data recovery, when the data recovery of the CTDB main node is abnormal, the corresponding mapping linked list is searched in the task list according to the task ID of the abnormal task, and the mapping linked list is removed from the task list. Because the mapping linked list contains the memory space address applied in advance, even if the system releases the memory space address due to the abnormal data recovery, the system can also ensure that the system can not obtain the internal slave space address in the task list when trying to execute the abnormal task again or perform the related monitoring of the abnormal task, thereby avoiding the core file generated by the system due to the fact that the memory space can not be found, further avoiding the crash of the CTDB and ensuring the reliability of the CTDB during data recovery.
On the basis of the third embodiment, the apparatus further includes:
the log recording module is used for recording the related information of the target recovery task to a task log representing an uncompleted task; the related information at least includes memory space capacity corresponding to the memory space address and a data recovery function.
Example four
The invention also provides a device for avoiding the crash of CTDB data during recovery, which comprises:
a memory for storing a computer program;
a processor for implementing the steps of the method for avoiding crash upon recovery of CTDB data as described above when executing a computer program.
According to the device for avoiding the crash of the CTDB data recovery, when the data recovery of the CTDB main node is abnormal, the corresponding mapping linked list is searched in the task list according to the task ID of the abnormal task, and the mapping linked list is removed from the task list. Because the mapping linked list contains the memory space address applied in advance, even if the system releases the memory space address due to the abnormal data recovery, the system can also ensure that the system can not obtain the internal slave space address in the task list when trying to execute the abnormal task again or perform the related monitoring of the abnormal task, thereby avoiding the core file generated by the system due to the fact that the memory space can not be found, further avoiding the crash of the CTDB and ensuring the reliability of the CTDB during data recovery.
The present invention also provides a computer readable storage medium having stored thereon a computer program which, when being executed by a processor, carries out the steps of the method for avoiding a crash upon recovery of CTDB data as described above.
According to the computer-readable storage medium for avoiding the crash of the CTDB data during recovery, when the data recovery performed by the CTDB main node is abnormal, the corresponding mapping linked list is searched in the task list according to the task ID of the abnormal task, and the mapping linked list is removed from the task list. Because the mapping linked list contains the memory space address applied in advance, even if the system releases the memory space address due to the abnormal data recovery, the system can also ensure that the system can not obtain the internal slave space address in the task list when trying to execute the abnormal task again or perform the related monitoring of the abnormal task, thereby avoiding the core file generated by the system due to the fact that the memory space can not be found, further avoiding the crash of the CTDB and ensuring the reliability of the CTDB during data recovery.
The method, apparatus and medium for avoiding crash of CTDB data during recovery provided by the present invention are described in detail above. 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. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, 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 various improvements and modifications to the present invention without departing from the principle of the present invention, and those improvements and modifications also fall within the scope of the claims of the present invention.
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 (10)
1. A method for avoiding crash of temporary database cluster data during recovery, comprising:
when the temporary database cluster master node executes a data recovery task, acquiring the current state of a target recovery task corresponding to a target task ID;
when the current state is abnormal, searching a mapping linked list corresponding to the target task ID in a task list; the mapping chain table comprises a data recovery function for executing the target recovery task and a pre-applied memory space address for caching recovery data, and the data recovery function and the memory space address have a mapping relation;
and removing the mapping linked list from the task list so as to avoid the crash of the temporary database cluster main node caused by accessing the memory space address.
2. The method of claim 1, wherein when the current state is abnormal, the method further comprises:
recording the related information of the target recovery task to a task log representing uncompleted tasks; wherein the related information at least includes the memory space capacity corresponding to the memory space address and the data recovery function.
3. The method of claim 2, wherein after recording the information related to the target recovery task to a task log representing uncompleted tasks, the method further comprises:
applying for a new memory space address in the temporary database cluster main node according to the memory space capacity, establishing a mapping relation between the new memory space address and the data recovery function, and generating a new mapping linked list;
and correspondingly recording the new mapping linked list and the new target task ID to the task list so as to be used for executing the target recovery task again.
4. The method according to claim 1, wherein the obtaining of the current state of the target recovery task corresponding to the target task ID specifically includes:
and acquiring the current state corresponding to the target task ID in a random mode.
5. Method according to claim 1, characterized in that the target task ID is in particular a random number in hexadecimal form.
6. Method according to any of claims 1 to 5, characterized in that the temporary database cluster master node is in particular a server running a Linux operating system.
7. An apparatus for avoiding crash upon recovery of temporary database cluster data, comprising:
the state acquisition module is used for acquiring the current state of the target recovery task corresponding to the target task ID when the temporary database cluster main node executes the data recovery task;
a linked list searching module, configured to search, when the current state is abnormal, a mapping linked list corresponding to the target task ID in a task list; the mapping chain table comprises a data recovery function for executing the target recovery task and a pre-applied memory space address for caching recovery data, and the data recovery function and the memory space address have a mapping relation;
and the linked list removing module is used for removing the mapping linked list from the task list so as to avoid the crash of the temporary database cluster main node caused by accessing the memory space address.
8. The apparatus of claim 7, further comprising:
the log recording module is used for recording the related information of the target recovery task to a task log representing an uncompleted task; wherein the related information at least includes the memory space capacity corresponding to the memory space address and the data recovery function.
9. An apparatus for avoiding crash upon recovery of temporary database cluster data, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the method of avoiding crash upon recovery of temporary database cluster data according to any one of claims 1 to 6 when executing said computer program.
10. A computer-readable storage medium, having stored thereon a computer program which, when being executed by a processor, carries out the steps of the method of avoiding a crash upon recovery of temporary database cluster data according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810529591.XA CN108776628B (en) | 2018-05-29 | 2018-05-29 | Method, device and medium for avoiding crash during CTDB data recovery |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810529591.XA CN108776628B (en) | 2018-05-29 | 2018-05-29 | Method, device and medium for avoiding crash during CTDB data recovery |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108776628A CN108776628A (en) | 2018-11-09 |
| CN108776628B true CN108776628B (en) | 2021-10-15 |
Family
ID=64027920
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810529591.XA Active CN108776628B (en) | 2018-05-29 | 2018-05-29 | Method, device and medium for avoiding crash during CTDB data recovery |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108776628B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111666067A (en) * | 2020-06-22 | 2020-09-15 | 深圳壹账通智能科技有限公司 | Task new building method and device, computer equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2001047224A9 (en) * | 1999-12-22 | 2002-05-23 | Black River Communications Llc | System for automatically conferencing a caller to one or more members of a group |
| CN101639839A (en) * | 2008-07-30 | 2010-02-03 | 中兴通讯股份有限公司 | Method for searching multi-archive file based on temporary table |
| CN103092712A (en) * | 2011-11-04 | 2013-05-08 | 阿里巴巴集团控股有限公司 | Method and device for recovering interrupt tasks |
| CN103885855A (en) * | 2012-12-20 | 2014-06-25 | 航天信息股份有限公司 | Data backup and recovery method and data backup and recovery device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE102005001150B4 (en) * | 2005-01-10 | 2006-11-16 | Siemens Ag | Method for setting up distributed filters in a packet-oriented network based on abstract security specifications |
-
2018
- 2018-05-29 CN CN201810529591.XA patent/CN108776628B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2001047224A9 (en) * | 1999-12-22 | 2002-05-23 | Black River Communications Llc | System for automatically conferencing a caller to one or more members of a group |
| CN101639839A (en) * | 2008-07-30 | 2010-02-03 | 中兴通讯股份有限公司 | Method for searching multi-archive file based on temporary table |
| CN103092712A (en) * | 2011-11-04 | 2013-05-08 | 阿里巴巴集团控股有限公司 | Method and device for recovering interrupt tasks |
| CN103885855A (en) * | 2012-12-20 | 2014-06-25 | 航天信息股份有限公司 | Data backup and recovery method and data backup and recovery device |
Non-Patent Citations (2)
| Title |
|---|
| CTDB: An Integrated Chickpea Transcriptome Database for Functional and Applied Genomics;Mohit Verma等;《PLOS ONE》;20151231;第10卷(第8期);全文 * |
| 一种Samba流量统计系统的设计与实现;文莎等;《信息通信》;20151031(第10期);第79-81页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108776628A (en) | 2018-11-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11237864B2 (en) | Distributed job scheduler with job stealing | |
| US9251233B2 (en) | Merging an out of synchronization indicator and a change recording indicator in response to a failure in consistency group formation | |
| CN106980699B (en) | Data processing platform and system | |
| CN108804253B (en) | Parallel operation backup method for mass data backup | |
| US9274876B2 (en) | Diagnostic data set component | |
| US10949401B2 (en) | Data replication in site recovery environment | |
| JP6445049B2 (en) | Log management method and computer system | |
| CN105573859A (en) | Data recovery method and device of database | |
| US11061889B2 (en) | Systems and methods of managing manifest refresh in a database | |
| US11468011B2 (en) | Database management system | |
| CN109460345B (en) | Real-time data calculation method and system | |
| US10223205B2 (en) | Disaster recovery data sync | |
| US8271454B2 (en) | Circular log amnesia detection | |
| US11113251B2 (en) | Transaction manager | |
| CN112261114A (en) | Data backup system and method | |
| CN114968966A (en) | Distributed metadata remote asynchronous replication method, device and equipment | |
| CN108776628B (en) | Method, device and medium for avoiding crash during CTDB data recovery | |
| CN102902770A (en) | Method and system for assembling mirror image files | |
| CN106815318B (en) | Clustering method and system for time sequence database | |
| US9619479B1 (en) | Autonomous deduplication for efficient recovery for a deduplication system | |
| JP2010238194A (en) | Operation management system, device, program, and method for analyzing process | |
| CN113806309A (en) | Metadata deleting method, system, terminal and storage medium based on distributed lock | |
| CN108271420A (en) | Manage method, file system and the server system of file | |
| CN117453454A (en) | Data backup method, device, computer equipment, medium and product | |
| CN111797062B (en) | Data processing method, device and distributed database system |
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 |