CN112565403B - Application node self-isolation method and device and electronic equipment - Google Patents
Application node self-isolation method and device and electronic equipment Download PDFInfo
- Publication number
- CN112565403B CN112565403B CN202011397882.1A CN202011397882A CN112565403B CN 112565403 B CN112565403 B CN 112565403B CN 202011397882 A CN202011397882 A CN 202011397882A CN 112565403 B CN112565403 B CN 112565403B
- Authority
- CN
- China
- Prior art keywords
- isolation
- normal
- abnormal
- strategy
- application
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1034—Reaction to server failures by a load balancer
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1029—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers using data related to the state of servers by a load balancer
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Debugging And Monitoring (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention discloses a self-isolation method and a self-isolation device of an application node and electronic equipment, wherein the method comprises the following steps: carrying out initialization check on the application node; if the initialization check is successful, judging whether a database connected with the application node is normal or not; if the connected database is abnormal, judging whether the abnormal condition meets a preset self-isolation strategy or not, and if the abnormal condition meets the preset self-isolation strategy, forwarding the request to other application nodes in normal states; if the connected database is normal, judging whether the user-defined health check of the application node is normal; and when the self-defined health check state of the application is abnormal and the abnormal condition meets a preset self-isolation strategy, forwarding the request to the application nodes in other normal states. The embodiment of the invention can automatically isolate the current link and transfer the flow to other application nodes in normal state after the database node fails in the application running process, thereby saving the labor cost and improving the fault repairing efficiency.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for self-isolating an application node, and an electronic device.
Background
Most applications today are based on F5 and soft load balancing (nginx) for traffic distribution. Most application architecture deployments are based on paas (Platform-as-a-Service) containerization management. Pass is a business model that provides the running and development environment of application services as a service. When the method is applied to production operation, if the bottom layer of the container breaks down, operation and maintenance personnel are required to manually isolate the nodes after receiving monitoring alarm information, and flow is redistributed.
At present, the self health check mechanism of the application using the paas platform is not perfect enough, and the state of the database is not detected. In addition, the application has F5 and soft load balancing modules for double-layer load balancing on the architecture deployment, and if F5 penetrates through soft load balancing (nginx) to activate the application, no unified strategy is available for determining whether the current node needs to be isolated. And once the node running state is abnormal, the node needs to be manually offline, and automatic isolation cannot be realized.
Accordingly, the prior art is yet to be improved and developed.
Disclosure of Invention
In view of the above deficiencies of the prior art, an object of the present invention is to provide a method, an apparatus, and an electronic device for self-isolation of an application node, which aim to solve the technical problem that a large amount of labor cost is consumed because a node needs to be manually offline when the operation state of a middle node of a paas platform is abnormal in the prior art.
The technical scheme of the invention is as follows:
a method of application node self-isolation, the method comprising:
carrying out initialization check on the application node;
if the initialization check is successful, judging whether a database connected with the application node is normal or not;
if the connected database is abnormal, judging whether the abnormal condition meets a preset self-isolation strategy or not, if the abnormal condition meets the preset self-isolation strategy, starting a fusing strategy, and forwarding the request to other application nodes in normal states;
if the connected database is normal, judging whether the user-defined health check of the application node is normal; and when the user-defined health check state of the application is abnormal and the abnormal condition meets a preset self-isolation strategy, starting a fusing strategy and forwarding the request to other application nodes with normal states.
Further, the performing initialization check on the application node further includes:
if the initialization check is detected to be failed, recording abnormal conditions, and judging whether the abnormal conditions meet a preset self-isolation strategy or not;
and if the preset self-isolation strategy is met, starting a fusing strategy, and forwarding the request to other application nodes in normal states.
Further preferably, if the connected database is abnormal, determining whether the abnormal condition meets a preset self-isolation policy includes:
if the connected database is abnormal, sending a fault alarm, recording abnormal times and returning a check result;
and judging whether a preset self-isolation strategy is met or not according to the checking result.
Further preferably, the determining whether the preset self-isolation policy is satisfied according to the checking result further includes:
and if the checking result does not meet the preset self-isolation strategy, performing initialization checking on the application node.
Preferably, when the customized health check state of the application is abnormal and the abnormal condition meets a preset self-isolation policy, the method starts a fusing policy, and forwards the request to an application node with a normal state, and further includes:
when the self-defined health check state of the application is abnormal, recording abnormal times, returning a check result, and judging whether a preset self-isolation strategy is met or not according to the check result;
if the preset self-isolation strategy is met, starting a fusing strategy, and forwarding the request to other application nodes in normal states;
and if the preset self-isolation strategy is not met, performing initialization check on the application node.
Further, after determining whether the customized health check of the application node is normal, the method further includes:
and if the self-defined health check state of the application node is normal, returning a correct health check result.
Further, the starting of the fusing policy forwards the request to other application nodes in normal states, including:
and updating the fusing parameters, executing a fusing strategy, and forwarding the request to other application nodes in normal states.
Another embodiment of the present invention provides an application node self-isolation apparatus, including:
the initialization checking module is used for carrying out initialization checking on the application nodes;
the database state checking module is used for judging whether the database connected with the application node is normal or not if the initialization checking is successful;
the database exception handling module is used for judging whether the abnormal condition meets a preset self-isolation strategy or not if the connected database is abnormal, starting a fusing strategy if the abnormal condition meets the preset self-isolation strategy, and forwarding the request to other application nodes in normal states;
the user-defined health exception processing module is used for judging whether the user-defined health check of the application node is normal or not if the connected database is normal; and when the custom health check state of the application is abnormal and the abnormal condition meets a preset self-isolation strategy, starting a fusing strategy and forwarding the request to the application nodes in other normal states.
Another embodiment of the present invention provides an electronic device, comprising a processor and a memory;
the memory is used for storing operation instructions;
the processor is configured to execute the application node self-isolation method according to any one of the above descriptions by calling the operation instruction.
Another embodiment of the present invention also provides a non-transitory computer-readable storage medium storing a computer program, which when executed by a processor, implements the application node self-isolation method described in any one of the above.
Has the beneficial effects that: the embodiment of the invention can automatically isolate the current link and transfer the flow to other application nodes in normal states by realizing that when the database node fails in the application running process, thereby saving the labor cost and improving the fault repairing efficiency.
Drawings
The invention will be further described with reference to the accompanying drawings and examples, in which:
FIG. 1 is a flow chart of a preferred embodiment of a method for self-isolation of application nodes according to the present invention;
FIG. 2 is a schematic structural diagram of a preferred embodiment of an application node self-isolation apparatus according to the present invention;
fig. 3 is a schematic structural diagram of an electronic device according to a preferred embodiment of the invention.
Detailed Description
In order to make the objects, technical solutions and effects of the present invention clearer and clearer, the present invention is described in further detail below. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. Embodiments of the present invention are described below with reference to the accompanying drawings.
The embodiment of the invention provides a self-isolation method of an application node. Referring to fig. 1, fig. 1 is a flow chart of a preferred embodiment of a method for self-isolation of an application node according to the present invention. As shown in fig. 1, it includes the steps of:
step S100, carrying out initialization check on the application node, judging whether the initialization check is successful, and if the initialization check is successful, executing step S200; if the initialization check is detected to fail, recording an abnormal condition, and executing the step S500;
step S200, judging whether the database connected with the application node is normal, and if the connected database is normal, executing step S300; if the connected database is abnormal, executing step S500;
step S300, judging whether the user-defined health check of the application node is normal, if so, executing step S400, and if not, executing step S500;
s400, returning a correct health check result;
s500, judging whether the abnormal condition meets a preset self-isolation strategy or not; if the abnormal condition meets the preset self-isolation strategy, executing the step S600; if the abnormal condition does not meet the preset self-isolation strategy, executing the step S100;
and step S600, starting a fusing strategy, and forwarding the request to other application nodes in normal states.
In specific implementation, the application node self-isolation algorithm in the embodiment of the invention is applied to NGINX to realize communication among F5, NGINX, APP and DB.
Step S100 is preceded by configuring an initialization health check. The user can configure the content needing health check in the initialization process according to the requirement. During the initialization process, the contents of the configured health check are checked. Judging whether the initialization check is successful;
if the initialization check is successful, initiating deep health check, penetrating into a database connected with the APP at the moment, judging whether the database is normal, and judging whether the user-defined health check is normal after the database is normal; the custom health check is a check item set by the user according to the characteristics of the application. For example, the custom health check may be a message delivery success check. The message is sent in order to check whether the application can communicate normally. If the message is detected to be successfully sent, the self-defined health check is normal; and if the message sending failure is detected, the self-defined health check is abnormal.
And when the initialization check is successful, the database is normal and the user-defined health check is normal, returning to the health check normal module without any isolation processing.
When any one of the initialization check, the database or the user-defined health check is detected to be abnormal, judging whether the abnormal condition meets a preset self-isolation strategy or not;
if the self-isolation strategy meets the preset self-isolation strategy, starting a fusing strategy, forwarding the request to other application nodes in normal states, and completing the self-isolation of the current fault application node;
if the preset self-isolation strategy is not met, repeating the steps S100 to S600 until a health check normal result is returned or the request is forwarded to other application nodes in normal states. Where a request refers to a request to access an application node.
In the embodiment of the invention, in the application running process, after the F5-database node fails, the current link is automatically isolated, and the flow is transferred to other nodes with normal states. And a self-isolation mechanism of the application node with a fault is realized by configuring a deep health inspection strategy.
Further, when the abnormal condition is that the initialization check fails, step S500 is to report the initialization abnormal condition, and after recording the initialization abnormal parameter, further determine whether to comply with the self-isolation policy according to the abnormal parameter. If the self-isolation strategy is that the number of times of abnormality reaches a preset threshold value, the initialization abnormal parameters need to be recorded. For example, if the predetermined threshold is 3 times, the self-isolation policy is executed when the number of recording initialization exceptions is 3 or more. The preset isolation strategy can be temporarily determined that three health checks fail continuously, and the actual strategy can be established according to project requirements.
Further, when the abnormal condition is database abnormality or application of custom check fails, step S500 specifically is to send a failure alarm, record the number of abnormality times, and return a check result if the connected database is abnormal; and judging whether a preset self-isolation strategy is met or not according to the checking result.
Further, if the checking result does not meet the preset self-isolation strategy, performing initialization checking on the application node. Considering that the application may be only temporarily offline or failed, the application node needs to be re-detected only when the detection result does not meet the preset self-isolation strategy and the detection result does not meet the preset self-isolation strategy, so that the generation of false alarms is reduced, and the utilization rate of the application node can be better improved.
Further, starting a fusing policy, and forwarding the request to other application nodes in normal states, specifically:
and updating the fusing parameters, executing a fusing strategy, and forwarding the request to other application nodes in normal states.
In specific implementation, the fusing parameters are periodically monitored through the fusing module, and when the abnormal condition in the application node meets the self-isolation strategy, the fusing parameters are updated, and the fusing strategy is executed. NGINX forwards the request to another APP node.
As can be seen from the above method embodiments, the embodiment of the present invention provides an application node self-isolation method, which adjusts a health check policy, extends a check link to a database server, and implements deep health check;
NGINX performs deep health checks on the hanging APP node, first checking the backend server state, and penetrating to check whether the database request is responded to. If no response is obtained, returning a health check error value; if the response is obtained, then a self-defined health check module (such as a message sending module) is applied to obtain a response sending health check normal value, and if the response is not obtained, a health check failure message is returned;
meanwhile, an isolation strategy is formulated, for example, the isolation strategy is configured to be a failure result obtained in three consecutive checks. If the deep health check fails three times continuously, a fusing mechanism is started. NGINX provides a fusing module, and monitors the health state of APP nodes hung down by NGINX. And when the state of the node hung under the NGINX is abnormal, the traffic is forwarded to other nodes.
It should be noted that, a certain order does not necessarily exist between the above steps, and those skilled in the art can understand, according to the description of the embodiments of the present invention, that in different embodiments, the above steps may have different execution orders, that is, may be executed in parallel, may also be executed interchangeably, and the like.
Another embodiment of the present invention provides an application node self-isolation apparatus, as shown in fig. 2, an apparatus 1 includes:
an initialization checking module 11, configured to perform initialization checking on the application node;
the database state checking module 12 is configured to, if it is detected that the initialization check is successful, determine whether a database connected to the application node is normal;
the database exception handling module 13 is configured to, if the connected database is abnormal, determine whether an abnormal condition meets a preset self-isolation policy, and if the abnormal condition meets the preset self-isolation policy, start a fusing policy and forward the request to an application node in a normal state;
the custom health exception processing module 14 is configured to, if the connected database is normal, determine whether the custom health check of the application node is normal; and when the user-defined health check state of the application is abnormal and the abnormal condition meets a preset self-isolation strategy, starting a fusing strategy and forwarding the request to other application nodes with normal states.
The specific implementation manner is described in the above method embodiments, and details are not repeated here.
Optionally, the initialization checking module 11 is further configured to record an abnormal condition if it is detected that the initialization checking fails, and determine whether the abnormal condition satisfies a preset self-isolation policy;
and if the preset self-isolation strategy is met, starting a fusing strategy, and forwarding the request to other application nodes in normal states.
Optionally, the database exception handling module 13 is further configured to send a fault alarm if the connected database is abnormal, record the number of abnormal times, and return a check result;
and judging whether a preset self-isolation strategy is met or not according to the checking result.
Optionally, the database exception handling module 13 is further configured to perform initialization inspection on the application node if the inspection result does not satisfy the preset self-isolation policy.
Optionally, the custom check module 14 is further configured to, when the custom health check state of the application is abnormal, record the number of times of abnormality, return a check result, and determine whether a preset self-isolation policy is satisfied according to the check result;
if the preset self-isolation strategy is met, starting a fusing strategy, and forwarding the request to other application nodes in normal states;
and if the preset self-isolation strategy is not met, performing initialization check on the application node.
The starting of the fusing policy and the forwarding of the request to the application nodes in other normal states specifically include: and updating the fusing parameters, executing a fusing strategy, and forwarding the request to other application nodes in normal states.
Optionally, the custom check module 14 is further configured to return a correct health check result if the custom health check status of the application node is normal.
Another embodiment of the present invention provides an electronic device 10, as shown in fig. 3, including a processor 110 and a memory 120;
a memory 120 for storing operating instructions;
the processor 110 is configured to execute the application node self-isolation method according to any one of the above descriptions by calling the operation instruction.
The processor 110 is used to implement various control logic for the electronic device 10, which may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a single chip microcomputer, an ARM (Acorn RISC machine) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of these components. Also, the processor 110 may be any conventional processor, microprocessor, or state machine. Processor 110 may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
The memory 120 may include a storage program area and a storage data area, wherein the storage program area may store an application program required for operating the device, at least one function; the storage data area may store data created from use of the electronic device 10, and the like. Further, the memory 120 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some embodiments, the memory 120 optionally includes memory located remotely from the processor 110, which may be connected to the electronic device 10 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
One or more units are stored in the memory 120, which when executed by the processor 110, perform the application node self-isolation method in any of the above-described method embodiments, e.g. performing the above-described method steps S100 to S600 in fig. 1.
An embodiment of the present invention provides a non-transitory computer-readable storage medium, which stores a computer program, and the computer program enables a processor to implement any one of the above-described application node self-isolation method rows when the computer program is executed, for example, to execute the above-described method steps S100 to S600 in fig. 1.
By way of example, non-volatile storage media can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), electrically erasable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM), which acts as external cache memory. By way of illustration and not limitation, RAM is available in many forms such as Synchronous RAM (SRAM), dynamic RAM, (DRAM), Synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The disclosed memory components or memory of the operating environment described herein are intended to comprise one or more of these and/or any other suitable types of memory.
The embodiments described above are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the embodiment.
Through the above description of the embodiments, it is clear to those skilled in the art that the embodiments may be implemented by software plus a general hardware platform, and may also be implemented by hardware. Based on such understanding, the technical solutions in essence or part contributing to the related art can be embodied in the form of a software product, which can be present in a computer readable storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the method of various embodiments or some parts of embodiments.
Conditional language such as "can," "might," or "may" is generally intended to convey that a particular embodiment can include (yet other embodiments do not include) particular features, elements, and/or operations, among others, unless specifically stated otherwise or understood otherwise within the context as used. Thus, such conditional language is also generally intended to imply that features, elements and/or operations are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without input or prompting, whether these features, elements and/or operations are included or are to be performed in any particular embodiment.
What has been described herein in the specification and drawings includes examples that can provide application node self-isolation methods and apparatus. It will, of course, not be possible to describe every conceivable combination of components and/or methodologies for purposes of describing the various features of the disclosure, but it can be appreciated that many further combinations and permutations of the disclosed features are possible. It is therefore evident that various modifications can be made to the disclosure without departing from the scope or spirit thereof. In addition, or in the alternative, other embodiments of the disclosure may be apparent from consideration of the specification and drawings and from practice of the disclosure as presented herein. It is intended that the examples set forth in this specification and figures be considered in all respects as illustrative and not restrictive. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.
Claims (10)
1. An application node self-isolation method, comprising:
carrying out initialization check on the application node;
if the initialization check is successful, judging whether a database connected with the application node is normal or not;
if the connected database is abnormal, judging whether the abnormal condition meets a preset self-isolation strategy or not, if the abnormal condition meets the preset self-isolation strategy, starting a fusing strategy, and forwarding the request to other application nodes in normal states;
if the connected database is normal, judging whether the user-defined health check of the application node is normal; and when the user-defined health check state of the application node is abnormal and the abnormal condition meets a preset self-isolation strategy, starting a fusing strategy and forwarding the request to the application node with a normal state.
2. The method of claim 1, wherein the initializing the application node to check further comprises:
if the initialization check is detected to fail, recording abnormal conditions, and judging whether the abnormal conditions meet a preset self-isolation strategy or not;
and if the preset self-isolation strategy is met, starting a fusing strategy, and forwarding the request to other application nodes in normal states.
3. The method of claim 2, wherein if the connected database is abnormal, determining whether the abnormal condition satisfies a preset self-isolation policy comprises:
if the connected database is abnormal, sending a fault alarm, recording abnormal times and returning a check result;
and judging whether a preset self-isolation strategy is met or not according to the checking result.
4. The method according to claim 3, wherein the determining whether the preset self-isolation policy is satisfied according to the checking result further comprises:
and if the checking result does not meet the preset self-isolation strategy, performing initialization checking on the application node.
5. The method of claim 1, wherein when the custom health check status of the application node is abnormal and the abnormal status satisfies a preset self-isolation policy, the method starts a fusing policy and forwards the request to other application nodes with normal statuses, and further comprising:
when the user-defined health check state of the application node is abnormal, recording the abnormal times, returning a check result, and judging whether a preset self-isolation strategy is met or not according to the check result;
if the preset self-isolation strategy is met, starting a fusing strategy, and forwarding the request to other application nodes in normal states;
and if the preset self-isolation strategy is not met, performing initialization check on the application node.
6. The method of claim 1, wherein after determining whether the custom health check of the application node is normal, further comprising:
and if the self-defined health check state of the application node is normal, returning a correct health check result.
7. The method of claim 1, wherein initiating the fusing policy and forwarding the request to other application nodes in a normal state comprises:
and updating the fusing parameters, executing a fusing strategy, and forwarding the request to other application nodes in normal states.
8. An application node self-isolation apparatus, comprising:
the initialization checking module is used for carrying out initialization checking on the application nodes;
the database state checking module is used for judging whether the database connected with the application node is normal or not if the initialization checking is successful;
the database exception handling module is used for judging whether the abnormal condition meets a preset self-isolation strategy or not if the connected database is abnormal, starting a fusing strategy if the abnormal condition meets the preset self-isolation strategy, and forwarding the request to other application nodes in normal states;
the user-defined health exception processing module is used for judging whether the user-defined health check of the application node is normal or not if the connected database is normal; and when the user-defined health check state of the application node is abnormal and the abnormal condition meets a preset self-isolation strategy, starting a fusing strategy and forwarding the request to the application node with a normal state.
9. An electronic device comprising a processor and a memory;
the memory is used for storing operation instructions;
the processor is used for executing the method of any one of claims 1-7 by calling the operation instruction.
10. A non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores a computer program that, when executed by a processor, implements the method of any one of claims 1-7.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202011397882.1A CN112565403B (en) | 2020-12-04 | 2020-12-04 | Application node self-isolation method and device and electronic equipment |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202011397882.1A CN112565403B (en) | 2020-12-04 | 2020-12-04 | Application node self-isolation method and device and electronic equipment |
Publications (2)
Publication Number | Publication Date |
---|---|
CN112565403A CN112565403A (en) | 2021-03-26 |
CN112565403B true CN112565403B (en) | 2022-09-06 |
Family
ID=75047935
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202011397882.1A Active CN112565403B (en) | 2020-12-04 | 2020-12-04 | Application node self-isolation method and device and electronic equipment |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN112565403B (en) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102932210A (en) * | 2012-11-23 | 2013-02-13 | 北京搜狐新媒体信息技术有限公司 | Method and system for monitoring node in PaaS cloud platform |
CN108446111A (en) * | 2018-03-26 | 2018-08-24 | 国家电网公司客户服务中心 | A kind of micro services construction method based on Spring cloud |
CN108595333A (en) * | 2018-04-26 | 2018-09-28 | Oppo广东移动通信有限公司 | The health examination method and device of application process in PaaS platform |
CN110609732A (en) * | 2019-08-13 | 2019-12-24 | 平安普惠企业管理有限公司 | Application program deployment method and device, computer equipment and storage medium |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070286087A1 (en) * | 2006-06-13 | 2007-12-13 | International Business Machines Corporation | Distributed Network Enhanced Wellness Checking |
-
2020
- 2020-12-04 CN CN202011397882.1A patent/CN112565403B/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102932210A (en) * | 2012-11-23 | 2013-02-13 | 北京搜狐新媒体信息技术有限公司 | Method and system for monitoring node in PaaS cloud platform |
CN108446111A (en) * | 2018-03-26 | 2018-08-24 | 国家电网公司客户服务中心 | A kind of micro services construction method based on Spring cloud |
CN108595333A (en) * | 2018-04-26 | 2018-09-28 | Oppo广东移动通信有限公司 | The health examination method and device of application process in PaaS platform |
CN110609732A (en) * | 2019-08-13 | 2019-12-24 | 平安普惠企业管理有限公司 | Application program deployment method and device, computer equipment and storage medium |
Also Published As
Publication number | Publication date |
---|---|
CN112565403A (en) | 2021-03-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN108173911B (en) | Micro-service fault detection processing method and device | |
CN108834086B (en) | Method and device for sending short message, computer equipment and storage medium | |
CN107566508A (en) | A kind of short message micro services system for automating O&M | |
CN108196940B (en) | Method for deleting container and related equipment | |
CN105553993A (en) | Remote service dispatching method and device and server | |
US20200204401A1 (en) | Method and device for automatically implementing ioam encapsulation and storage medium | |
US20200382365A1 (en) | Updating software in cloud gateways | |
CN108848054B (en) | Network equipment registration method and device, computer equipment and storage medium | |
CN101022638A (en) | Alarm reporting method and alarm device | |
CN109213507A (en) | A kind of upgrade method and server | |
CN112070585A (en) | Order state unified management method and device, computer equipment and storage medium | |
EP4030776A1 (en) | Method and apparatus for triggering vomci function from olt to send omci messages | |
CN112565403B (en) | Application node self-isolation method and device and electronic equipment | |
CN107465756B (en) | Service request processing method and device | |
CN113312059A (en) | Service processing system and method and cloud native system | |
KR102275065B1 (en) | Apparatus and method for security control | |
US10382301B2 (en) | Efficiently calculating per service impact of ethernet ring status changes | |
CN112738264B (en) | Message middleware message transmission method and device, computer equipment and storage medium | |
CN109547439B (en) | Processing method and device for service node access network | |
CN112214466B (en) | Distributed cluster system, data writing method, electronic equipment and storage device | |
CN112988405B (en) | Automatic degradation method and device for micro-service and computing equipment | |
CN107819648B (en) | Method and device for detecting NETCONF connection of network configuration | |
CN110166528B (en) | Method and device for preventing node change notification from being lost and computer equipment | |
CN114691395A (en) | Fault processing method and device, electronic equipment and storage medium | |
CN109067611B (en) | Method, device, storage medium and processor for detecting communication state between systems |
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 |