CN113687929A - Exception handling method and related device - Google Patents
Exception handling method and related device Download PDFInfo
- Publication number
- CN113687929A CN113687929A CN202110975231.4A CN202110975231A CN113687929A CN 113687929 A CN113687929 A CN 113687929A CN 202110975231 A CN202110975231 A CN 202110975231A CN 113687929 A CN113687929 A CN 113687929A
- Authority
- CN
- China
- Prior art keywords
- exception handling
- target service
- service
- state information
- self
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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/52—Program synchronisation; Mutual exclusion, e.g. by means of semaphores
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Retry When Errors Occur (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses an exception handling method, which comprises the following steps: when the service self-checking component detects that the target service is abnormal, judging whether an abnormal processing process for executing operation on the target service exists or not; when the exception handling process does not exist, state information of the target service is acquired; and when the state information is inactive, executing exception handling operation on the target service through the service self-checking component. When the service self-checking assembly detects an abnormality, whether an abnormal processing process for executing operation on the target service exists is judged, and whether the state information is inactive is determined when the abnormal processing process does not exist, so that the simultaneous existence of the abnormal processing process for operating is avoided, other processes are prevented from just completing the processing of the target service, the target service does not need to be processed abnormally again, the problem of mutual exclusion is avoided, and the experience of operating a file system is improved. The application also discloses an exception handling device, a server and a computer readable storage medium, which have the beneficial effects.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to an exception handling method, an exception handling apparatus, a server, and a computer-readable storage medium.
Background
With the continuous development of data storage technology, more and more functions appear in a file system to cope with complex use scenarios. Smb (Server Messages Block) is a component of ceph (distributed file system) file system, and provides smb service for sharing out directories and files on the file system. Taking a windows client as an example, the shared folder of smb can be mounted by mapping a network driver, and the shared folder is mapped to a network disk of windows.
In the related art, when the management software configures smb a service, a restart smb command is issued, and at this time, the restart is divided into two flows, namely, stop and start. When executing to stop, just as the ctdb (Cluster Database) monitors smb to be in stop state, the ctdb will also execute restart smb to pull smb service up. When ctdb executes stop, the management software just executes start smb, so that the start of the tube software is cancelled, and the tube software reports an error to restart smb and fails. Similarly, when ctdb is servicing restart smb, if the management software happens to issue a restart smb command, ctdb will report an error to restart smb. Therefore, the mutual exclusion problem of a plurality of resource access resources is easy to occur in the corresponding management software, and the experience of operating the file system is reduced.
Therefore, how to avoid the mutual exclusion problem of accessing resources is a key issue of attention for those skilled in the art.
Disclosure of Invention
The application aims to provide an exception handling method, an exception handling device, a server and a computer readable storage medium, so as to avoid the problem of mutual exclusion during exception handling and improve the experience of operating a file system.
In order to solve the above technical problem, the present application provides an exception handling method, including:
when the service self-checking component detects that the target service is abnormal, judging whether an abnormal processing process for executing operation on the target service exists or not;
when the exception handling process does not exist, acquiring state information of the target service;
and when the state information is inactive, executing exception handling operation on the target service through the service self-checking component.
Optionally, when the service self-checking component detects that the target service is abnormal, determining whether an abnormal processing process for executing an operation on the target service exists, including:
and when the service self-checking component detects that the port of the target service is not occupied, judging whether the abnormal processing process issued by the management software exists or not.
Optionally, when the service self-checking component detects that the port of the target service is not occupied, determining whether the exception handling process issued by the management software exists includes:
and when the service self-checking component detects that the port of the target service is not occupied, judging whether an ism _ pid process issued by the management software exists or not.
Optionally, the method further includes:
and when the exception handling process exists, executing termination operation on the exception handling operation of the service self-checking assembly, and performing exception handling on the target service through the exception handling process.
Optionally, when the exception handling process does not exist, obtaining the state information of the target service includes:
and when the exception handling process does not exist, acquiring the state information of the target service through a query command.
Optionally, when the state information is inactive, executing an exception handling operation on the target service through the service self-checking component, where the exception handling operation includes:
and when the state information is not active, executing restart operation on the target service through the service self-checking component.
Optionally, the method further includes:
and when the state information is active, executing termination operation on the abnormal processing operation of the service self-checking assembly.
The present application further provides an exception handling apparatus, including:
the process judgment module is used for judging whether an abnormal processing process for executing operation on the target service exists or not when the service self-inspection component detects that the target service is abnormal;
the state acquisition module is used for acquiring the state information of the target service when the exception handling process does not exist;
and the exception handling module is used for executing exception handling operation on the target service through the service self-checking component when the state information is inactive.
The present application further provides a server, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the exception handling method as described above when executing the computer program.
The present application also provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the exception handling method as described above.
The application provides an exception handling method, which comprises the following steps: when the service self-checking component detects that the target service is abnormal, judging whether an abnormal processing process for executing operation on the target service exists or not; when the exception handling process does not exist, acquiring state information of the target service; and when the state information is inactive, executing exception handling operation on the target service through the service self-checking component.
When the service self-checking assembly detects an abnormality, whether an abnormal processing progress for executing operation on the target service exists is judged, namely whether other progresses exist for abnormal processing is determined, whether state information is inactive is determined when the abnormal processing progress does not exist, and finally abnormal processing operation is performed, so that the phenomenon that the abnormal processing progress for operation exists at the same time is avoided, the phenomenon that other progresses to finish processing the target service just now is avoided, the target service does not need to be processed abnormally again, the problem of mutual exclusion is avoided finally, and the experience of operating a file system is improved.
The present application further provides an exception handling apparatus, a server, and a computer-readable storage medium, which have the above beneficial effects and are not described herein again.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of an exception handling method according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of an exception handling apparatus according to an embodiment of the present disclosure.
Detailed Description
The core of the application is to provide an exception handling method, an exception handling device, a server and a computer readable storage medium, so as to avoid the problem of mutual exclusion during exception handling and improve the experience of operating a file system.
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the related art, when the management software configures smb a service, a restart smb command is issued, and at this time, the restart is divided into two flows, namely, stop and start. When executing to stop, just as the ctdb (Cluster Database) monitors smb to be in stop state, the ctdb will also execute restart smb to pull smb service up. When ctdb executes stop, the management software just executes start smb, so that the start of the tube software is cancelled, and the tube software reports an error to restart smb and fails. Similarly, when ctdb is servicing restart smb, if the management software happens to issue a restart smb command, ctdb will report an error to restart smb. Therefore, the mutual exclusion problem of a plurality of resource access resources is easy to occur in the corresponding management software, and the experience of operating the file system is reduced.
Therefore, according to the exception handling method provided by the application, when the service self-checking component detects an exception, whether an exception handling process for executing an operation on the target service exists is judged, namely whether other processes perform exception handling is determined, whether state information is inactive is determined when the exception handling process does not exist, and finally exception handling operation is performed, so that the problem that an exception handling process for performing an operation exists at the same time is avoided, other processes do not need to perform exception handling again when the target service is processed completely, the problem of mutual exclusion is avoided finally, and the experience of operating a file system is improved.
An exception handling method provided by the present application is described below with reference to an embodiment.
Referring to fig. 1, fig. 1 is a flowchart illustrating an exception handling method according to an embodiment of the present disclosure.
In this embodiment, the method may include:
s101, when the service self-checking component detects that the target service is abnormal, judging whether an abnormal processing progress for executing operation on the target service exists or not;
therefore, the step aims to judge whether an exception handling process for executing operation on the target service exists or not when the service self-checking component detects that the target service is abnormal. That is, the service self-check component determines whether the target service is abnormal. When the target service is judged to be abnormal, the problem of operation failure caused by simultaneous operation on the target service is avoided.
Further, the step may include:
and when the service self-checking component detects that the port of the target service is not occupied, judging whether an abnormal processing process issued by the management software exists or not.
It can be seen that the alternative scheme mainly explains how to detect and judge. In this alternative, when the service self-checking component detects that the target port is not occupied, it is determined whether an exception handling process issued by the management software exists. Thus, it is conceivable that the port that needs to be served to the target destination in this alternative is occupied. If yes, the target service is normal and no abnormity exists. If not, the target service is abnormal.
For example, in smb service, when smb service starts, 445 and 139 ports are in an occupied state. Therefore, the ctdb executes a monitor event every 5s, and the monitor event calls the ctdb checktcpport 445 to detect whether the 445 port of smb is occupied, specifically, the method includes attempting to bind the 445 port, if the binding is successful, it indicates that the changed port is not occupied, and if the binding is failed, it indicates that the changed port is occupied by smb service. If 445 port is occupied indicating smb is in good service, otherwise 445 port is not occupied indicating smb is in poor service.
Further, the above alternatives may also include:
when the service self-checking component detects that the port of the target service is not occupied, whether an ism _ pid process issued by management software exists is judged.
It can be seen that this alternative is mainly to illustrate how the determination is made. In this alternative, when the service self-checking component detects that the port of the target service is not occupied, it is determined whether an ism _ pid process issued by the management software exists. Wherein, the ism _ pid process is a process for performing a restart operation on the smb by the management software.
S102, when the exception handling process does not exist, state information of the target service is obtained;
on the basis of S101, this step is intended to acquire state information of the target service when there is no exception handling process.
That is, when there is no exception handling process, it cannot be determined that there is no problem with exception handling of the target service at this time. It also needs to be judged by the status information of the target service. I.e., determine if the target service has just been exception-handled. Therefore, in this step, the state information of the target service needs to be acquired.
Wherein the status information is active or inactive. When the state information is active, the target service is just completed by exception processing, and the exception processing is not required to be carried out again. When the state information is inactive, it indicates that the target service has not executed the corresponding exception handling operation yet, and the exception handling operation needs to be executed.
Further, the step may include:
and when the exception handling process does not exist, acquiring the state information of the target service through the query command.
It can be seen that the present alternative is mainly to explain how to obtain the status information. In this alternative, when there is no exception handling process, the state information of the target service is acquired by the query command. The query command may be any one of query commands provided in the prior art, and is not specifically limited herein.
In addition, the present embodiment may further include:
and when an exception handling process exists, executing termination operation on the exception handling operation of the service self-checking assembly, and performing exception handling on the target service through the exception handling process.
It can be seen that the present alternative is primarily illustrative of how to handle when an exception handling process is present. In this alternative, if the exception handling process exists, it indicates that a process for handling the target service exists at this time, and the service self-checking component does not need to perform exception handling any more, and needs to stop processing related to the service self-checking component.
And S103, when the state information is inactive, executing exception handling operation on the target service through the service self-checking component.
On the basis of S102, this step is intended to perform an exception handling operation on the target service through the service self-checking component when the state information is inactive.
Further, the step may include:
and when the state information is inactive, executing restart operation on the target service through the service self-checking component.
It can be seen that the present alternative is primarily illustrative of how exception handling may be performed. In this alternative, when the state information is inactive, a restart operation is performed on the target service through the service self-checking component.
In addition, the present embodiment may further include:
and when the state information is active, executing termination operation on the exception handling operation of the service self-checking component.
It can be seen that this alternative is primarily illustrative of how the state information may be handled when active. When the state information is active, it indicates that the exception handling process just completed the exception handling of the target service, and needs to perform the exception handling again, and it is sufficient to perform the termination operation on the related operation.
To sum up, in this embodiment, when the service self-checking component detects an exception, it is determined whether an exception handling process for executing an operation on the target service exists, that is, it is determined whether another process exists at this time to perform exception handling, and it is determined whether state information is inactive when the exception handling process does not exist, and finally, an exception handling operation is performed, so that an exception handling process for performing an operation is avoided, and it is also avoided that another process has just completed processing the target service, and no exception handling is performed again on the target service, so that a mutual exclusion problem is finally avoided, and experience of operating the file system is improved.
The exception handling method provided by the present application is further described below by a specific embodiment.
In this embodiment, the method may include:
step 1, when a service self-checking component detects that a port of a target service is not occupied, judging whether an ism _ pid process issued by management software exists or not;
step 2, when an exception handling process exists, executing termination operation on the exception handling operation of the service self-checking assembly, and performing exception handling on the target service through the exception handling process;
step 3, when no abnormal processing process exists, acquiring the state information of the target service through the query command;
step 4, when the state information is inactive, restarting the target service through the service self-checking component;
and 5, when the state information is active, executing termination operation on the abnormal processing operation of the service self-checking assembly.
Based on the above steps, in a specific application scenario, the above operation steps may be applied to the technical field where ctdb handles smb exceptions.
The steps of this embodiment may include:
step 1, when ctdb detects smb abnormal service, checking whether a process ism _ pid for managing soft start or restart smb exists;
step 2, if the ism _ pid process exists, the ctdb restart smb process automatically exits, and the managed software restart smb process continues;
step 3, if ism _ pid process does not exist, this indicates that either ism _ pid process has just exited or no process has started smb. At this time, the status of smb needs to be checked by a systemctl status smb command for further judgment;
step 4, if the smb state is active, it indicates that the ism _ pid process just exits, smb is already started, and ctdb does not need to restart smb, and then ctdb is responsible for restarting smb child process to exit;
step 5, if the smb status is inactive, it indicates that the ism _ pid process has not occurred, and the smb status is still abnormal, and ctdb is required to restart smb service.
It can be seen that, in the embodiment, when the service self-checking component detects an exception, it is determined whether an exception handling process for executing an operation on the target service exists, that is, it is determined whether another process exists at this time to perform exception handling, and it is determined whether state information is inactive when the exception handling process does not exist, and finally, an exception handling operation is performed again, so that an exception handling process for performing an operation is avoided, and it is also avoided that another process has just completed processing the target service, and it is not necessary to perform exception handling again on the target service, and finally, a mutual exclusion problem is avoided, and experience of operating a file system is improved.
In the following, the exception handling apparatus provided in the embodiment of the present application is introduced, and the exception handling apparatus described below and the exception handling method described above may be referred to correspondingly.
Referring to fig. 2, fig. 2 is a schematic structural diagram of an exception handling apparatus according to an embodiment of the present disclosure.
In this embodiment, the apparatus may include:
the process judgment module 100 is configured to, when the service self-inspection component detects that the target service is abnormal, judge whether an abnormal processing process for executing an operation on the target service exists;
a state obtaining module 200, configured to obtain state information of a target service when there is no exception handling process;
and the exception handling module 300 is used for executing exception handling operation on the target service through the service self-checking component when the state information is inactive.
Optionally, the process determining module 100 is specifically configured to determine whether an exception handling process issued by the management software exists when the service self-inspection component detects that the port of the target service is not occupied.
Optionally, the process determining module 100 is specifically configured to determine whether an ism _ pid process issued by the management software exists when the service self-inspection component detects that the port of the target service is not occupied.
Optionally, the apparatus may further include:
and the first termination module is used for executing termination operation on the abnormal processing operation of the service self-checking assembly when an abnormal processing progress exists, and performing abnormal processing on the target service through the abnormal processing progress.
Optionally, the state obtaining module 200 is specifically configured to obtain the state information of the target service through a query command when there is no exception handling process.
Optionally, the exception handling module 300 is specifically configured to, when the state information is inactive, execute a restart operation on the target service through the service self-checking component.
Optionally, the apparatus may further include:
and the second termination module is used for executing termination operation on the abnormal processing operation of the service self-checking assembly when the state information is active.
An embodiment of the present application further provides a server, including:
a memory for storing a computer program;
a processor for implementing the steps of the exception handling method as described in the above embodiments when executing the computer program.
The embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the steps of the exception handling method according to the above embodiment.
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.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The foregoing detailed description of an exception handling method, an exception handling apparatus, a server, and a computer-readable storage medium provided by the present application. The principles and embodiments of the present application are explained herein using specific examples, which are provided only to help understand the method and the core idea of the present application. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
Claims (10)
1. An exception handling method, comprising:
when the service self-checking component detects that the target service is abnormal, judging whether an abnormal processing process for executing operation on the target service exists or not;
when the exception handling process does not exist, acquiring state information of the target service;
and when the state information is inactive, executing exception handling operation on the target service through the service self-checking component.
2. The exception handling method according to claim 1, wherein when the self-service inspection component detects that the target service is abnormal, determining whether there is an exception handling process for performing an operation on the target service, includes:
and when the service self-checking component detects that the port of the target service is not occupied, judging whether the abnormal processing process issued by the management software exists or not.
3. The exception handling method according to claim 2, wherein when the service self-checking component detects that the port of the target service is not occupied, determining whether the exception handling process issued by management software exists includes:
and when the service self-checking component detects that the port of the target service is not occupied, judging whether an ism _ pid process issued by the management software exists or not.
4. The exception handling method according to claim 1, further comprising:
and when the exception handling process exists, executing termination operation on the exception handling operation of the service self-checking assembly, and performing exception handling on the target service through the exception handling process.
5. The exception handling method according to claim 1, wherein obtaining the state information of the target service when the exception handling process does not exist comprises:
and when the exception handling process does not exist, acquiring the state information of the target service through a query command.
6. The exception handling method according to claim 1, wherein when said state information is inactive, performing an exception handling operation on said target service by said service self-test component, comprises:
and when the state information is not active, executing restart operation on the target service through the service self-checking component.
7. The exception handling method according to claim 1, further comprising:
and when the state information is active, executing termination operation on the abnormal processing operation of the service self-checking assembly.
8. An exception handling apparatus, comprising:
the process judgment module is used for judging whether an abnormal processing process for executing operation on the target service exists or not when the service self-inspection component detects that the target service is abnormal;
the state acquisition module is used for acquiring the state information of the target service when the exception handling process does not exist;
and the exception handling module is used for executing exception handling operation on the target service through the service self-checking component when the state information is inactive.
9. A server, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the exception handling method of any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, characterized in that a computer program is stored thereon, which computer program, when being executed by a processor, carries out the steps of the exception handling method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110975231.4A CN113687929B (en) | 2021-08-24 | 2021-08-24 | Exception handling method and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110975231.4A CN113687929B (en) | 2021-08-24 | 2021-08-24 | Exception handling method and related device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113687929A true CN113687929A (en) | 2021-11-23 |
| CN113687929B CN113687929B (en) | 2024-08-20 |
Family
ID=78581926
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110975231.4A Active CN113687929B (en) | 2021-08-24 | 2021-08-24 | Exception handling method and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113687929B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6467050B1 (en) * | 1998-09-14 | 2002-10-15 | International Business Machines Corporation | Method and apparatus for managing services within a cluster computer system |
| CN101299677A (en) * | 2008-04-30 | 2008-11-05 | 中兴通讯股份有限公司 | Method for sharing unity service course by multiple courses |
| CN102571965A (en) * | 2012-01-16 | 2012-07-11 | 浪潮(北京)电子信息产业有限公司 | Method and device for starting service group in high-availability cluster |
| US8627331B1 (en) * | 2010-04-30 | 2014-01-07 | Netapp, Inc. | Multi-level parallelism of process execution in a mutual exclusion domain of a processing system |
| CN111309627A (en) * | 2020-03-08 | 2020-06-19 | 苏州浪潮智能科技有限公司 | A method and system for preventing test conflict in software testing |
-
2021
- 2021-08-24 CN CN202110975231.4A patent/CN113687929B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6467050B1 (en) * | 1998-09-14 | 2002-10-15 | International Business Machines Corporation | Method and apparatus for managing services within a cluster computer system |
| CN101299677A (en) * | 2008-04-30 | 2008-11-05 | 中兴通讯股份有限公司 | Method for sharing unity service course by multiple courses |
| US8627331B1 (en) * | 2010-04-30 | 2014-01-07 | Netapp, Inc. | Multi-level parallelism of process execution in a mutual exclusion domain of a processing system |
| CN102571965A (en) * | 2012-01-16 | 2012-07-11 | 浪潮(北京)电子信息产业有限公司 | Method and device for starting service group in high-availability cluster |
| CN111309627A (en) * | 2020-03-08 | 2020-06-19 | 苏州浪潮智能科技有限公司 | A method and system for preventing test conflict in software testing |
Non-Patent Citations (1)
| Title |
|---|
| 佚名: "如何解决资源并发访问问题", HTTPS://ZHUANLAN.ZHIHU.COM/P/285686315, 11 November 2020 (2020-11-11) * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113687929B (en) | 2024-08-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107844343B (en) | Upgrading system and method for complex server application system | |
| CN102622298B (en) | Software testing system and method | |
| US20140130036A1 (en) | Methods and Systems for Automated Deployment of Software Applications on Heterogeneous Cloud Environments | |
| US10545807B2 (en) | Method and system for acquiring parameter sets at a preset time interval and matching parameters to obtain a fault scenario type | |
| CN104360952B (en) | A kind of software testing system and method | |
| CN108287769B (en) | Information processing method and device | |
| CN110063042A (en) | A kind of response method and its terminal of database failure | |
| CN111209110A (en) | Task scheduling management method, system and storage medium for realizing load balance | |
| CN110716922A (en) | Incep-based database operation and maintenance method and device, computer equipment and storage medium | |
| CN113407383A (en) | Main/standby system switching method and device, server and main/standby system | |
| CN111538585A (en) | Js-based server process scheduling method, system and device | |
| US7882399B2 (en) | Intelligent job functionality | |
| CN117806799A (en) | Batch task distributed scheduling method and device | |
| US20150220380A1 (en) | Dynamically determining an external systems management application to report system errors | |
| CN110727537A (en) | Method and device for uniformly processing response message, computer equipment and storage medium | |
| CN115629920A (en) | Data request exception handling method and device and computer readable storage medium | |
| CN105868957A (en) | Continuous integration method and device | |
| CN113687929A (en) | Exception handling method and related device | |
| CN113778763B (en) | Intelligent switching method and system for three-way interface service faults | |
| CN111654553B (en) | Middleware-based management and control operation method and device, computer equipment and medium | |
| CN114205231A (en) | Method and system for starting hadoop clusters in batch and readable storage medium | |
| CN115934272A (en) | Online batch task processing method and device | |
| CN118820008B (en) | Method, device and electronic equipment for monitoring controller status | |
| CN111984484A (en) | Non-invasive micro-service access method and system | |
| CN120030086B (en) | Multi-node CMDB block refined data synchronization method and 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 |