CN109032774B - Application program recovery method and device - Google Patents
Application program recovery method and device Download PDFInfo
- Publication number
- CN109032774B CN109032774B CN201810681782.8A CN201810681782A CN109032774B CN 109032774 B CN109032774 B CN 109032774B CN 201810681782 A CN201810681782 A CN 201810681782A CN 109032774 B CN109032774 B CN 109032774B
- Authority
- CN
- China
- Prior art keywords
- application
- task
- rollback
- program
- application program
- 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
Images
Classifications
-
- 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/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides an application program recovery method and device, and relates to the field of computer task execution. The method and the device for restoring the application program register a starting state and a rollback program entry in a pre-stored database application list when the application program is started; then acquiring and executing an application task; finally, after the operation lock is successfully acquired, when any session item associated with the application program in the starting state in the pre-established database session list does not contain the active database session, the rollback program is called according to the rollback program entry to roll back the task in execution to the initial state, so that corresponding services do not need to be deployed at the server and the monitoring end, the detection of the available state of the application without the center is realized, the extra monitoring cost is greatly reduced, the congestion of the computer system caused by the existence of the center node is avoided, the mutual recovery among the applications is realized, the recovery of the application without waiting for the crash is not required, and the recovery time of the computing system is greatly shortened.
Description
Technical Field
The invention relates to the field of computer task execution, in particular to an application program recovery method and device.
Background
A computer cluster (or cluster for short) is a computer system that performs computing tasks by connecting a set of loosely integrated computer hardware together in a highly compact collaboration. In a sense, they may be considered a computer. The individual computing devices in a cluster system are often referred to as nodes, and are typically connected by a network, although other connections are also possible. Clustered computers are commonly used to improve the computational speed and reliability of individual computers. High Availability (High Availability) refers to the ability of a computer system to perform its functions without interruption, represents the degree of Availability of the system, and is one of the criteria when designing the system. The measure of high availability is based on a comparison of system damage, time to fail, time to return from non-operational to operational status, and total system operational time. When cluster equipment and architecture are determined, the mean time between failures is only related to the stability of the service running on the cluster, and depends on the quality of the service implementation code, but currently, a general scheme for improving the code quality is difficult to find.
The application availability detection method in the conventional technology is generally divided into two parts: a first part: the index monitoring service is arranged on each server host computer needing to monitor the availability and is used for collecting available state index data applied to the server; the second part, the index collection service, is deployed on a host that collects the available state of the cluster server, generally a monitoring dedicated host, and the service polls each server in the cluster to obtain the information collected by the index monitoring service and performs statistical arrangement. For the sorted information, the service provides a query function at the same time, and the service can acquire the available state of the application on any one server in the cluster.
However, the above-mentioned application availability detection method needs to deploy corresponding services at the server and the monitoring end, and there is a certain limitation on the software operating environment of the server, and if the software operating environments of the servers in the cluster are very different, monitoring cannot be implemented due to the fact that monitoring end services suitable for all the servers cannot be found, and the cost for deploying corresponding services at the server and the monitoring end is very high; and the application availability detection depends on a single node, and a fault point cannot be timely found when the cluster size increases. Because the transmission network of the available state index data is in a star structure, the monitoring host at the central position polls the monitored nodes, although the index collection service can be deployed on each monitored node theoretically, the increase of the monitoring nodes can cause the flow of the index information in the cluster network to be multiplied, so the index collection service is generally deployed on the special monitoring host, and all collapse applications in the cluster can only wait for discovery of a few central nodes; and the application recovery completely depends on the application itself, and because the available states of the applications are unknown to each other, the crash recovery can only depend on the application itself, and if a certain application has a long failure time, the failure recovery process of the whole system can also last for a long time.
Disclosure of Invention
In view of the above, an object of the present invention is to provide an application recovery method and apparatus to improve the above-mentioned problems.
In a first aspect, an embodiment of the present invention provides an application program recovery method, where the application program recovery method includes:
when the application program is started, registering a starting state and a rollback program entry in a pre-stored database application list;
acquiring and executing an application task;
when the operation lock is successfully acquired, judging whether each session item associated with each application program in the pre-established database session list in the starting state contains an active database session;
when any one of the session items associated with the application program in the starting state in the pre-established database session list does not contain the active database session, the rollback program is called according to the rollback program entrance to roll back the task in execution to the starting state.
In a second aspect, an embodiment of the present invention further provides an application program recovery apparatus, where the application program recovery apparatus includes:
the information registration unit is used for registering a starting state and a rollback program entry in a pre-stored database application list when the application program is started;
the task execution unit is used for acquiring and executing the application task;
the judging unit is used for judging whether each session item associated with the application program in the starting state in the pre-established database session list contains an active database session when the operation lock is successfully acquired;
and the rollback unit is used for calling a rollback program according to a rollback program entry to rollback the task in execution to the initial state when any one session item associated with the application program in the starting state in the pre-established database session list does not contain the active database session.
Compared with the prior art, the method and the device for recovering the application program provided by the invention have the advantages that firstly, when the application program is started, the starting state and the rollback program entry are registered in the pre-stored database application list; then acquiring and executing an application task; finally, after the operation lock is successfully acquired, when any session item associated with the application program in the starting state in the pre-established database session list does not contain the active database session, the rollback program is called according to the rollback program entry to roll back the task in execution to the initial state, so that corresponding services do not need to be deployed at the server and the monitoring end, the detection of the available state of the application without the center is realized, the extra monitoring cost is greatly reduced, the congestion of the computer system caused by the existence of the center node is avoided, the mutual recovery among the applications is realized, the recovery of the application program without waiting for the collapse is not required, and the recovery time of the computing system is greatly shortened.
In order to make the aforementioned and other objects, features and advantages of the present invention comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, 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 some, but not all, embodiments of the present invention. The components of embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present invention, presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. 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 invention.
Fig. 1 is an interaction diagram of a cluster server system according to an embodiment of the present invention;
fig. 2 is a block diagram of a server according to an embodiment of the present invention;
FIG. 3 is a flowchart of an application recovery method according to an embodiment of the present invention;
fig. 4 is a functional unit diagram of an application recovery apparatus according to an embodiment of the present invention.
Icon: 100-a server; 200-application recovery means; 101-a processor; 102-a memory; 103-a memory controller; 401-an information registration unit; 402-a task execution unit; 403-sleep state entry unit; 404-a judging unit; 405-rollback unit.
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. The components of embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present invention, presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present invention without making any creative effort, shall fall within the protection scope of the present invention.
The method and apparatus for recovering an application program according to the preferred embodiment of the present invention can be applied to a server 100, where the server 100 is applied to a cluster server system, as shown in fig. 1, the cluster server system includes a plurality of servers 100, and a communication connection is established between the plurality of servers 100. The server 100 may be, but is not limited to, a web server, a database server, a cloud server, and the like. Fig. 2 shows a block diagram of a server applicable to an embodiment of the present invention. The server 100 includes an application recovery apparatus 200, a peripheral interface 104, a memory 102, a storage controller 103, and a processor 101.
The Memory 102 may be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM) of the ROM 102, a Programmable Read Only Memory (PROM), an Erasable Read Only Memory (EPROM), an electrically Erasable Read Only Memory (EEPROM), and the like. The memory 102 is configured to store a program, and the processor 101 executes the program after receiving an execution instruction, and the method executed by the server defined by the flow process disclosed in any of the foregoing embodiments of the present invention may be applied to the processor 101, or implemented by the processor 101.
The processor 101 may be an integrated circuit chip having signal processing capabilities. The Processor 101 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; but may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. The various methods, steps and logic blocks disclosed in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor 101 may be any conventional processor 101 or the like.
The peripheral interface 104 couples various input/output devices to the processor 101 as well as to the memory 102. In some embodiments, the peripheral interface 104, the processor 101, and the memory controller 103 may be implemented in a single chip. In other examples, they may be implemented separately from the individual chips.
Referring to fig. 3, an embodiment of the present invention provides an application program recovery method, where the application program recovery method includes:
step S301: when the application program is started, the starting state and the rollback program entry are registered in a pre-stored database application list.
Before the application program is started, the application program is in a non-starting state, and when a starting instruction input by a worker is received, the application program is started. The pre-stored database application list contains data content and status information of various application programs, at this time, only the starting status and the rollback program entry of the started application program are registered, and the application program can call the rollback program through the rollback program (i.e., the rollback program) entry.
Step S302: and acquiring and executing the application task.
When the application task is executed, the application task is executed according to the sequence of a plurality of processes forming the application task, wherein each process comprises process execution node information.
Specifically, after the application task is acquired and executed, the task execution process and the process execution node information may be stored in a preset cluster data sharing area. In order to realize parallel computing, data sharing among cluster servers is indispensable, and currently, two common data sharing modes are database sharing and network storage sharing, so that a preset cluster data sharing area is available, each server and each application program can access the cluster data sharing area, and processes, contents and process execution node information of executed tasks are executed.
Step S303: judging whether the operation lock is successfully acquired, if so, executing the step S305; if not, step S304 is performed.
The operation lock can comprise a shared lock and an exclusive lock, wherein the exclusive lock can only be provided with one thread at a time to hold the lock; the shared lock allows multiple threads to acquire the lock simultaneously and may access the shared resource concurrently. Monopolizing the lock avoids read/read conflicts, and if a certain read-only thread acquires the lock, other read threads can only wait, in which case unnecessary concurrency is limited, because the read operation does not affect the consistency of data. Shared locks relax the locking policy, allowing multiple threads performing read operations to access the shared resource simultaneously.
In this embodiment, the operation lock is preferably an exclusive lock of an application task included in the database application list or an exclusive lock of a network shared storage file, so that when a plurality of application programs in a starting state exist in the cluster server system, conflict possibly caused by simultaneous application program recovery can be avoided, and performance waste caused by detecting states of other application programs for many times is also avoided.
Step S304: and controlling the application program to be in the dormant state again.
After the device is in the dormant state again, the next starting instruction can be received, and the task is executed again.
Step S305: judging whether each session item associated with each application program in the starting state in a pre-established database session list contains an active database session; if not, step S306 is performed.
When the application program is connected with the database, a related database session list is pre-established in the database, and the database session list comprises information such as host names and application names, so that the availability of the application program can be judged through the database session list.
Step S306: and calling a rollback program according to the rollback program entrance to roll back the task in execution to the initial state.
Specifically, the rollback program may be called according to the rollback program entry, so that the rollback program rolls back the task in execution to the initial state according to the task execution process and the process execution node information located in the cluster data shared area, thereby completing recovery of the application program from running crash.
Step S307: the operation lock is released, and step S304 is performed after the operation lock is released.
After the device is in the dormant state again, the next starting instruction can be received, and the task is executed again.
In this embodiment, the operation state may be automatically recovered after the preset sleep time elapses, and the next operation period is started from S302, so that the operation is repeated.
Referring to fig. 4, an application recovery apparatus 200 is further provided in the embodiment of the present invention, it should be noted that the basic principle and the generated technical effect of the application recovery apparatus 200 provided in the embodiment are the same as those of the above embodiment, and for a brief description, corresponding contents in the above embodiment may be referred to where this embodiment is not mentioned. The application resuming device 200 includes an information registering unit 401, a task executing unit 402, a hibernation-state entering unit 403, a judging unit 404, and a rollback unit 405.
The information registration unit 401 is configured to register a start state and a rollback program entry in a pre-stored database application list when an application program starts.
It is to be understood that the information registration unit 401 may perform step S301 described above.
The task execution unit 402 is used to acquire and execute application tasks.
The task execution unit 402 is specifically configured to acquire and execute an application task, and store a task execution process and process execution node information in a preset cluster data sharing area.
It is to be understood that the task performing unit 402 may perform the above-described step S302.
The judgment unit 404 is used to judge whether the operation lock is successfully acquired.
It is understood that the judging unit 404 may perform the above-described step S303.
The sleep state entering unit 403 is used to control the application program to be in the sleep state again when the operation lock is not successfully acquired.
It is to be understood that the sleep-state entering unit 403 may perform the step S304 described above.
The determining unit 404 is configured to determine whether an active database session is included in session entries associated with each application program in the pre-established database session list in the startup state when the operation lock is successfully acquired.
It is to be understood that the judging unit 404 may also perform the above-described step S305.
The operation lock is an exclusive lock of an application task contained in the database application list or an exclusive lock of a network shared storage file.
The rollback unit 405 is configured to invoke a rollback program according to a rollback program entry to rollback an executing task to a starting state when any session item associated with an application in a start state in a pre-established database session list does not include an active database session.
The rollback unit 405 is specifically configured to invoke a rollback program according to a rollback program entry, so that the rollback program rolls back the task in execution to an initial state according to the task execution process and the process execution node information located in the cluster data sharing area.
It is to be understood that the rollback unit 405 may perform step S306 described above.
The sleep state entering unit 403 is used to release the operation lock and control the application program to enter the sleep state again.
It is to be understood that the sleep state entering unit 403 may perform the step S307 described above.
In summary, according to the method and apparatus for restoring an application program provided by the present invention, when the application program is started, a start state and a rollback program entry are registered in a pre-stored database application list; then acquiring and executing an application task; finally, after the operation lock is successfully acquired, when any session item associated with the application program in the starting state in the pre-established database session list does not contain the active database session, the rollback program is called according to the rollback program entry to roll back the task in execution to the initial state, so that corresponding services do not need to be deployed at the server and the monitoring end, the detection of the available state of the application without the center is realized, the extra monitoring cost is greatly reduced, the congestion of the computer system caused by the existence of the center node is avoided, the mutual recovery among the applications is realized, the recovery of the application without waiting for the crash is not required, and the recovery time of the computing system is greatly shortened.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method can be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, the functional modules in the embodiments of the present invention may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes. It is noted that, herein, relational terms such as first and second, and the like may be 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.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
It is noted that, herein, relational terms such as first and second, and the like may be 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. An application recovery method applied to a cluster server system, the application recovery method comprising:
when the application program is started, registering a starting state and a rollback program entry in a pre-stored database application list;
acquiring and executing an application task;
when the operation lock is successfully acquired, judging whether each session item associated with each application program in the pre-established database session list in the starting state contains an active database session;
when any one session item associated with the application program in the starting state in the pre-established database session list does not contain the active database session, calling a rollback program according to a rollback program entry to rollback an executing task to an initial state;
the step of obtaining and executing the application task comprises: acquiring and executing an application task, and storing a task execution process and process execution node information in a preset cluster data sharing area;
the step of calling the rollback program according to the rollback program entry to rollback the executing task to the initial state comprises the following steps:
and calling a rollback program according to the rollback program entrance so that the rollback program rolls back the task in execution to the initial state according to the task execution process and the process execution node information in the cluster data sharing area.
2. The method for recovering an application program according to claim 1, wherein the operation lock is an exclusive lock of an application task contained in the database application list or an exclusive lock of a network shared storage file.
3. The application recovery method of claim 1, wherein after the step of rolling back the task in execution to the start state by calling the rollback program according to the rollback program entry, the application recovery method further comprises:
and releasing the operation lock and controlling the application program to be in the dormant state again.
4. The application recovery method of claim 1, further comprising:
and when the operation lock is not successfully acquired, controlling the application program to be in the dormant state again.
5. An application recovery apparatus, applied to a cluster server system, the application recovery apparatus comprising:
the information registration unit is used for registering a starting state and a rollback program entry in a pre-stored database application list when the application program is started;
the task execution unit is used for acquiring and executing the application task;
the judging unit is used for judging whether each session item associated with the application program in the starting state in the pre-established database session list contains an active database session when the operation lock is successfully acquired;
the system comprises a rollback unit, a task execution unit and a task execution unit, wherein the rollback unit is used for calling a rollback program according to a rollback program entry to rollback an executing task to an initial state when any one session item associated with an application program in a starting state in a pre-established database session list does not contain an active database session;
the task execution unit is specifically used for acquiring and executing the application task, and storing the task execution process and the process execution node information in a preset cluster data sharing area;
the rollback unit is specifically configured to invoke a rollback program according to a rollback program entry, so that the rollback program rolls back the task in execution to an initial state according to the task execution process and the process execution node information located in the cluster data sharing area.
6. The application recovery apparatus according to claim 5, wherein the operation lock is an exclusive lock of an application task included in the database application list or an exclusive lock of a network shared storage file.
7. The application recovery apparatus of claim 5, further comprising:
and the dormant state entering unit is used for releasing the operation lock and controlling the application program to enter the dormant state again.
8. The application recovery apparatus of claim 5, further comprising:
and the dormant state entering unit is used for controlling the application program to be in the dormant state again when the operation lock is not successfully acquired.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810681782.8A CN109032774B (en) | 2018-06-27 | 2018-06-27 | Application program recovery method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810681782.8A CN109032774B (en) | 2018-06-27 | 2018-06-27 | Application program recovery method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109032774A CN109032774A (en) | 2018-12-18 |
| CN109032774B true CN109032774B (en) | 2021-08-13 |
Family
ID=65520574
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810681782.8A Active CN109032774B (en) | 2018-06-27 | 2018-06-27 | Application program recovery method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109032774B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113703946B (en) * | 2021-08-31 | 2023-07-14 | 中国联合网络通信集团有限公司 | Application recovery method and device, electronic equipment and computer readable storage medium |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB2409544A (en) * | 2003-12-24 | 2005-06-29 | Ibm | Involving participants in a distributed transaction |
| CN100365632C (en) * | 2006-04-05 | 2008-01-30 | 华为技术有限公司 | Processing method for realizing consistency of internal storage data and data bank data service |
| CN100472525C (en) * | 2006-06-09 | 2009-03-25 | 联想(北京)有限公司 | A system and method for realizing electronic bookmark |
| CN102141946B (en) * | 2011-03-25 | 2014-08-20 | 北京世纪互联宽带数据中心有限公司 | Method and system for recovering online transaction data in graph database |
| WO2012083697A1 (en) * | 2011-07-30 | 2012-06-28 | 华为技术有限公司 | Method and device for transaction recovery |
-
2018
- 2018-06-27 CN CN201810681782.8A patent/CN109032774B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN109032774A (en) | 2018-12-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6859889B2 (en) | Backup system and method for distributed systems | |
| JP6333410B2 (en) | Fault processing method, related apparatus, and computer | |
| JP4726416B2 (en) | Method for operating a computer cluster | |
| US8743680B2 (en) | Hierarchical network failure handling in a clustered node environment | |
| WO2017140131A1 (en) | Data writing and reading method and apparatus, and cloud storage system | |
| US9342426B2 (en) | Distributed system, server computer, distributed management server, and failure prevention method | |
| CN100359481C (en) | Abnormal monitoring equipment and method for multi-task system | |
| US7870248B2 (en) | Exploiting service heartbeats to monitor file share | |
| CN104391777B (en) | Cloud platform and its operation and monitoring method and device based on (SuSE) Linux OS | |
| CN105357042B (en) | A kind of highly available cluster system and its host node and from node | |
| US20220138036A1 (en) | Safely recovering workloads within a finite timeframe from unhealthy cluster nodes | |
| CN110955723A (en) | Master-slave database synchronization state monitoring method and device and electronic equipment | |
| US10740166B2 (en) | Thread based dynamic data collection | |
| CN109032774B (en) | Application program recovery method and device | |
| CN111831408A (en) | Asynchronous task processing method and device, electronic equipment and medium | |
| WO2009123343A1 (en) | Contention analysis device, contention analysis method, and program | |
| CN106899659B (en) | Distributed system and management method and management device thereof | |
| US11544091B2 (en) | Determining and implementing recovery actions for containers to recover the containers from failures | |
| JP2735514B2 (en) | Process status management method | |
| Dinu et al. | Hadoop’s overload tolerant design exacerbates failure detection and recovery | |
| JP2018180982A (en) | Information processing device and log recording method | |
| KR19990013389A (en) | Method and apparatus for rolling up the case | |
| JP3269489B2 (en) | Process monitoring system and process monitoring method | |
| CN113886490A (en) | Method and system for realizing high availability of stateless computing instances in distributed database | |
| EP3070610B1 (en) | Information processing device, control method thereof, and recording 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 |