CN112671601B - Interface monitoring system and method based on Zookeeper - Google Patents
Interface monitoring system and method based on Zookeeper Download PDFInfo
- Publication number
- CN112671601B CN112671601B CN202011459120.XA CN202011459120A CN112671601B CN 112671601 B CN112671601 B CN 112671601B CN 202011459120 A CN202011459120 A CN 202011459120A CN 112671601 B CN112671601 B CN 112671601B
- Authority
- CN
- China
- Prior art keywords
- node
- master node
- slave
- interface
- monitoring
- 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
- 238000012544 monitoring process Methods 0.000 title claims abstract description 77
- 238000000034 method Methods 0.000 title claims abstract description 28
- 230000036541 health Effects 0.000 claims description 12
- 238000013475 authorization Methods 0.000 claims description 6
- 238000004422 calculation algorithm Methods 0.000 claims description 6
- 230000000737 periodic effect Effects 0.000 claims description 6
- 230000002159 abnormal effect Effects 0.000 claims description 4
- 238000002347 injection Methods 0.000 claims description 4
- 239000007924 injection Substances 0.000 claims description 4
- 238000005516 engineering process Methods 0.000 abstract description 8
- 238000004364 calculation method Methods 0.000 abstract description 5
- 230000001419 dependent effect Effects 0.000 abstract description 5
- 238000012423 maintenance Methods 0.000 abstract description 5
- 238000012545 processing Methods 0.000 abstract description 5
- 238000009877 rendering Methods 0.000 abstract description 5
- 230000009286 beneficial effect Effects 0.000 abstract description 4
- 210000004556 brain Anatomy 0.000 abstract description 4
- 230000000007 visual effect Effects 0.000 abstract description 3
- 238000011161 development Methods 0.000 description 10
- 238000003032 molecular docking Methods 0.000 description 3
- 238000004590 computer program Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000005538 encapsulation Methods 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000000926 separation method Methods 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 230000002567 autonomic effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
Landscapes
- Debugging And Monitoring (AREA)
- Small-Scale Networks (AREA)
Abstract
The application discloses a Zookeeper-based interface monitoring system and a Zookeeper-based interface monitoring method, wherein the system comprises a loading configuration unit, a node management unit and an interface monitoring unit; the loading configuration unit is used for loading a configuration file to obtain a configuration instruction; the node management unit utilizes the distributed coordination characteristic of the Zookeeper to manage the competition of the cluster nodes, and the master node is selected in an competing way, so that the master node is used as the brain of the system to control the business of the whole cluster; the interface monitoring unit is used for monitoring the conditions of all interfaces; the application utilizes the Zookeeper technology to realize the monitoring of high concurrency interface access and the processing of real-time data, and provides visual front-end page display; the front page adopts VUE and other technologies, can automatically track the dependent template expression and calculation attribute, adopts declarative rendering, and is more beneficial to the expansion and maintenance of the system.
Description
Technical Field
The application relates to the field of system interface monitoring, in particular to a Zookeeper-based interface monitoring system and a Zookeeper-based interface monitoring method.
Background
In the context of the rapid evolution of the internet today, the number of internet users is increasing, resulting in geometrically increasing access pressures, and single systems have failed to meet the high concurrency support. The method can perform longitudinal expansion or transverse expansion to meet high concurrency access in a data layer, a system layer and an access layer, and can perform targeted optimization on specific high concurrency modules, such as building a cache, a newly added load balancing system, newly added queue consumption and the like.
The method for monitoring the calling condition and the interface state of each interface in real time in the interface docking application system is critical to the efficient and stable operation of the system, but the method for monitoring the calling condition and the interface state of each interface in real time in the interface docking application system is still lacking in the prior art.
The application utilizes the Zookeeper technology to realize the monitoring of high concurrency interface access and the processing of real-time data, and provides visual front-end page display. The front page adopts VUE and other technologies, can automatically track the dependent template expression and calculation attribute, adopts declarative rendering, and is more beneficial to the expansion and maintenance of the system.
Disclosure of Invention
In order to solve the problem that the calling condition and the interface state of each interface are difficult to monitor in real time in an interface docking application system in the prior art, the application provides an interface monitoring system based on a Zookeeper, which comprises:
the loading configuration unit is connected with the node management unit at one end; the loading configuration unit is used for loading a configuration file to obtain a configuration instruction and sending the configuration instruction to the node management unit;
the node management unit comprises a node operation module and a registration monitoring module; the node management unit adopts a Zookeeper framework;
the node operation module comprises 1 master node, M slave nodes and N load nodes; the M, N are all positive integers; the main node is used for sending a main node instruction and a main node heartbeat packet to the registration monitoring module according to the configuration instruction, and running a plug-in; the slave node is used for operating the plug-in unit according to the master node instruction, and judging whether to elect a new master node according to the master node heartbeat packet and a preset rule; the load node is used for sending a load distribution request to the registration monitoring module according to the main node instruction and a load algorithm;
one end of the registration monitoring module is connected with the node operation module and is used for sending the master node instruction to the slave node and the load node, sending the heartbeat packet of the master node to the slave node and sending the load distribution request to the master node and the slave node;
the interface monitoring unit is connected with the node management unit at one end; the interface monitoring unit is used for monitoring the conditions of all the interfaces.
Further, the system comprises a web service access function which is constructed based on a Dropwizard framework, a dependency injection which is realized based on a guide framework and a tangent plane oriented function.
Further, the system further comprises:
the plug-in extension unit is connected with the node management unit at one end; the plug-in expansion unit is used for independently developing plug-ins and providing the plug-ins for the node management unit;
the system initialization unit is connected with the loading configuration unit, the node management unit and the plug-in extension unit; the system initialization unit is used for realizing the functions of initializing the system during starting, background periodic scheduling task, health degree checking and service managed.
Further, the slave node is further configured to send a heartbeat packet of the slave node to the registration monitoring module; the registration monitoring module is further used for sending the heartbeat packet of the slave node to the master node; the master node is also used for judging whether the corresponding slave node operates normally or not according to the slave node heartbeat packet; and if the slave node is abnormally operated, removing the abnormal operation slave node information from the storage.
Further, the slave node judging whether to elect a new master node according to the master node heartbeat packet and a preset rule includes:
the M slave nodes detect the heartbeat packet of the master node, and if the P slave nodes judge that the master node runs abnormally, the master node is selected from the M slave nodes and acts as the master node; wherein, P is more than or equal to 1 and less than or equal to M.
Furthermore, the interface monitoring unit adopts a VUE framework to monitor the conditions of all interfaces.
Further, the monitoring the conditions of each interface includes:
monitoring configuration of interface monitoring, interface authorization condition, interface calling condition, interface liveness and interface health state.
The interface monitoring method based on the Zookeeper comprises the following steps:
acquiring a configuration instruction;
according to the configuration instruction, the master node sends a master node heartbeat packet to the slave node, sends a master node instruction to the slave node and the load node, and operates the plug-in;
the slave node operates a plug-in according to the master node instruction, and judges whether to elect a new master node according to the master node heartbeat packet and a preset rule;
the load node sends a load distribution request to the master node and the slave node according to the master node instruction and a load algorithm;
the master node, the slave node and the load node are managed based on a Zookeeper;
the condition of each interface is monitored.
Further, before acquiring the configuration instruction, the method further comprises:
initializing a system;
the master node, the slave node, and the load node register based on a Zookeeper.
Further, the method further comprises:
the slave node sends a slave node heartbeat packet to the master node; the master node judges whether the corresponding slave node operates normally according to the slave node heartbeat packet; and if the slave node is abnormally operated, removing the abnormal operation slave node information from the storage.
Further, the number of the master nodes is 1, the number of the slave nodes is M, and the number of the load nodes is N; the M, N are all positive integers; the slave nodes judge whether to elect a new master node according to the master node heartbeat packet and a preset rule, wherein if P slave nodes judge that the master node operates abnormally according to the master node heartbeat packet, the slave nodes elect the master node and act as the master node from M slave nodes; wherein, P is more than or equal to 1 and less than or equal to M.
Further, the method comprises the step of monitoring the condition of each interface by adopting a VUE framework.
Further, the monitoring the conditions of each interface includes:
monitoring configuration of interface monitoring, interface authorization condition, interface calling condition, interface liveness and interface health state.
The beneficial effects of the application are as follows: the application provides a Zookeeper-based interface monitoring system and a Zookeeper-based interface monitoring method, wherein the system comprises a loading configuration unit, a node management unit and an interface monitoring unit; the loading configuration unit is used for loading a configuration file to obtain a configuration instruction; the node management unit utilizes the distributed coordination characteristic of the Zookeeper to manage the competition of the cluster nodes, and the master node is selected in an competing way, so that the master node is used as the brain of the system to control the business of the whole cluster; the interface monitoring unit is used for monitoring the conditions of all interfaces; the application utilizes the Zookeeper technology to realize the monitoring of high concurrency interface access and the processing of real-time data, and provides visual front-end page display; the front page adopts VUE and other technologies, can automatically track the dependent template expression and calculation attribute, adopts declarative rendering, and is more beneficial to the expansion and maintenance of the system.
Drawings
Exemplary embodiments of the present application may be more completely understood in consideration of the following drawings:
FIG. 1 is a block diagram of a Zookeeper-based interface monitoring system according to an embodiment of the present application;
fig. 2 is a flowchart of a Zookeeper-based interface monitoring method according to an embodiment of the present application.
Detailed Description
The exemplary embodiments of the present application will now be described with reference to the accompanying drawings, however, the present application may be embodied in many different forms and is not limited to the examples described herein, which are provided to fully and completely disclose the present application and fully convey the scope of the application to those skilled in the art. The terminology used in the exemplary embodiments illustrated in the accompanying drawings is not intended to be limiting of the application. In the drawings, like elements/components are referred to by like reference numerals.
Unless otherwise indicated, terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art. In addition, it will be understood that terms defined in commonly used dictionaries should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense.
Fig. 1 is a block diagram of an interface monitoring system based on Zookeeper according to an embodiment of the present application. As shown in fig. 1, the system includes:
a loading configuration unit 110, wherein one end of the loading configuration unit 110 is connected with the node management unit 120; the loading configuration unit 110 is configured to load a configuration file to obtain a configuration instruction, and send the configuration instruction to the node management unit 120;
specifically, the system in this example includes supporting a web service access function built based on a Dropwizard framework, dependency injection implemented based on a guide framework, and a tangent plane oriented function; the configuration file comprises relevant information of the master node and the slave nodes, relevant information of each node operation plugin, load node load distribution request information and the like; or the slave node may be automatically discovered when the system is started.
A node management unit 120, where the node management unit 120 includes a node operation module 1201 and a registration monitoring module 1202; the node management unit 120 adopts a Zookeeper framework;
the node operation module 1201 comprises 1 master node, M slave nodes and N load nodes; the M, N are all positive integers; the master node is configured to send a master node instruction and a master node heartbeat packet to the registration monitor module 1202 according to the configuration instruction, and run a plugin; the slave node is used for operating the plug-in unit according to the master node instruction, and judging whether to elect a new master node according to the master node heartbeat packet and a preset rule; the load node is configured to send a load distribution request to the registration monitor module 1202 according to the master node instruction and a load algorithm;
further, the slave node is further configured to send a slave node heartbeat packet to the registration monitor module 1202; the registration monitor module 1202 is further configured to send the slave node heartbeat packet to the master node; the master node is also used for judging whether the corresponding slave node operates normally or not according to the slave node heartbeat packet; if the slave node is abnormally operated, the information of the abnormally operated slave node is removed from the storage;
further, the slave node judging whether to elect a new master node according to the master node heartbeat packet and a preset rule includes:
the M slave nodes detect the heartbeat packet of the master node, and if the P slave nodes judge that the master node runs abnormally, the master node is selected from the M slave nodes and acts as the master node; wherein P is more than or equal to 1 and less than or equal to M;
specifically, in this example, M takes 20 and p takes 10, that is, if more than half of the slave nodes find that the master node is abnormally operated, the master node is selected from the slave nodes, and the selected master node acts as the master node;
one end of the registration monitoring module 1202 is connected with the node running module 1201, and is configured to send the master node instruction to the slave node and the load node, send the heartbeat packet of the master node to the slave node, and send the load distribution request to the master node and the slave node;
specifically, the registration monitor module 1202 in this example uses the distributed coordination feature of the Zookeeper to implement registration and monitoring on various nodes to manage competition of the cluster nodes, so that the master node serves as a brain of the system to control the service of the whole cluster.
An interface monitoring unit 130, wherein one end of the interface monitoring unit 130 is connected with the node management unit 120; the interface monitoring unit 130 is configured to monitor conditions of each interface;
specifically, in this example, the interface monitoring unit 130 implements front-end page display by using a VUE frame, so as to monitor the conditions of each interface in real time; the monitoring of the conditions of each interface comprises: monitoring configuration, interface authorization condition, interface calling condition, interface liveness and interface health state of interface monitoring; by adopting the technologies of VUE and the like, the dependent template expression and calculation attribute can be automatically tracked, and declarative rendering is adopted, so that the expansion and maintenance of the system are facilitated.
A system initialization unit 140, where the system initialization unit 140 is connected to the loading configuration unit 110, the node management unit 120, the interface monitoring unit 130, and the plug-in extension unit 150; the system initialization unit 140 is configured to implement functions including a system startup initialization function, a background periodic scheduling task function, a health check function, and a service managed function;
specifically, the initializing function in this example includes initializing tasks such as registration binding before the plug-in is started; the background periodic scheduling task function comprises functions such as registration binding and the like; the health check function comprises the steps of detecting whether the plug-in running environment is healthy or not before starting, if so, testing the connection condition of a database, and if so, failing to start the system; the service managed functions include initiating a shutdown operation, such as establishing a connection with a database, etc.
A plug-in extension unit 150, wherein one end of the plug-in extension unit 150 is connected with the node management unit 120; the plug-in extension unit 150 is configured to autonomously develop a plug-in and provide the plug-in to the node management unit 120;
further, the autonomic development plug-in includes:
front-end and back-end separated plug-in development mode, namely back-end code plug-in development, front-end plug-in deployment mapping; front and back end code plug-in development without plug-in development separation; therefore, when the plug-in package is deployed, only the developed plug-in package is required to be deployed, so that the expanded service or the service provided by the outside can be met; the plug-in is mainly aimed at a certain task or external service, the configuration files of all the plug-ins are independent, the configuration files special for the plug-in can be customized, the maximum normal operation node number and the minimum normal operation number are configured in the plug-in configuration files, and when the node for operating the plug-in is hung off, the plug-in can be transferred to a service node which does not start the plug-in; when the plug-in is run by nodes that are not satisfied, i.e., all running nodes run the plug-in, and less than the minimum number of running nodes, the system generates an alarm.
Furthermore, the system performs encapsulation processing on part of the database, so that related operations can be directly performed without the need of adding configuration, package leading and other operations by a user; the database includes mysql, oracle, sqlServer, mongodb, etc.; while the system encapsulates and simplifies access to the redis cache and provides a mainstream toolkit, jackson, metrics, etc.
Fig. 2 is a flowchart of a Zookeeper-based interface monitoring method according to an embodiment of the present application. As shown in fig. 2, the method includes:
step 210, system initialization and node registration; the system initialization comprises an initialization function when the system is started, a background periodic scheduling task function, a health degree checking function and a service managed function; the master node, the slave node and the load node are registered based on a Zookeeper;
specifically, the initializing function in this example includes initializing tasks such as registration binding before the plug-in is started; the background periodic scheduling task function comprises functions such as registration binding and the like; the health check function comprises the steps of detecting whether the plug-in running environment is healthy or not before starting, if so, testing the connection condition of a database, and if so, failing to start the system; the service managed functions include initiating a shutdown operation, such as establishing a connection with a database, etc.
Step 220, obtaining a configuration instruction; specifically, the configuration instruction in this example includes relevant information of the master node and the slave node, relevant information of each node operation plugin, load node load distribution request information, and the like; the system comprises a web service access function which is constructed based on a Dropwizard framework, a dependency injection which is realized based on a guide framework and a tangent plane oriented function.
Step 230, judging whether to elect a new master node and run a plug-in; according to the configuration instruction, a main node instruction is sent to the slave node and the load node, and a plug-in is operated; the slave node operates a plug-in according to the master node instruction;
further, the slave node sends a slave node heartbeat packet to the master node; the master node judges whether the corresponding slave node operates normally according to the slave node heartbeat packet; if the slave node is abnormally operated, the information of the abnormally operated slave node is removed from the storage;
according to the configuration instruction, the master node sends a master node heartbeat packet to the slave node, and the slave node judges whether to elect a new master node according to the master node heartbeat packet and a preset rule;
further, the number of the master nodes is 1, the number of the slave nodes is M, and the number of the load nodes is N; the M, N are all positive integers; the slave nodes judge whether to elect a new master node according to the master node heartbeat packet and a preset rule, wherein if P slave nodes judge that the master node operates abnormally according to the master node heartbeat packet, the slave nodes elect the master node and act as the master node from M slave nodes; wherein P is more than or equal to 1 and less than or equal to M;
specifically, in this example, M takes 20 and p takes 10, that is, if more than half of the slave nodes find that the master node is abnormally operated, the master node is selected from the slave nodes, and the selected master node acts as the master node;
further, the load node sends a load distribution request to the master node and the slave node according to the master node instruction and a load algorithm;
furthermore, the master node, the slave node and the load node are managed based on the Zookeeper, and the registration and monitoring of various nodes are realized by utilizing the distributed coordination characteristic of the Zookeeper so as to manage the competition of the cluster nodes, so that the master node is used as a brain of a system to control the business of the whole cluster.
Step 240, monitoring the condition of each interface; specifically, in the embodiment, a VUE frame is adopted to realize front-end page display, so that the condition of each interface is monitored in real time; the monitoring of the conditions of each interface comprises: monitoring configuration, interface authorization condition, interface calling condition, interface liveness and interface health state of interface monitoring; by adopting the technologies of VUE and the like, the dependent template expression and calculation attribute can be automatically tracked, and declarative rendering is adopted, so that the expansion and maintenance of the system are facilitated.
Step 250, independently developing plug-ins; independently developing plug-ins under the master node and the slave nodes according to requirements;
specifically, the autonomous development plugin in this example includes: front-end and back-end separated plug-in development mode, namely back-end code plug-in development, front-end plug-in deployment mapping; front and back end code plug-in development without plug-in development separation; therefore, when the plug-in package is deployed, only the developed plug-in package is required to be deployed, so that the expanded service or the service provided by the outside can be met; the plug-in is mainly aimed at a certain task or external service, the configuration files of all the plug-ins are independent, the configuration files special for the plug-in can be customized, the maximum normal operation node number and the minimum normal operation number are configured in the plug-in configuration files, and when the node for operating the plug-in is hung off, the plug-in can be transferred to a service node which does not start the plug-in; when the plug-in is run by nodes that are not satisfied, i.e., all running nodes run the plug-in, and less than the minimum number of running nodes, the system generates an alarm.
Furthermore, the system performs encapsulation processing on part of the database, so that related operations can be directly performed without the need of adding configuration, package leading and other operations by a user; the database includes mysql, oracle, sqlServer, mongodb, etc.; while the system encapsulates and simplifies access to the redis cache and provides a mainstream toolkit, jackson, metrics, etc.
In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the disclosure may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Those skilled in the art will appreciate that the modules in the apparatus of the embodiments may be adaptively changed and disposed in one or more apparatuses different from the embodiments. The modules or units or components of the embodiments may be combined into one module or unit or component and, furthermore, they may be divided into a plurality of sub-modules or sub-units or sub-components. Any combination of all features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or units of any method or apparatus so disclosed, may be used in combination, except insofar as at least some of such features and/or processes or units are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings), may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise. Reference to step numbers in this specification is used solely to distinguish between steps and is not intended to limit the time or logical relationship between steps, including the various possible conditions unless the context clearly indicates otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features but not others included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the disclosure and form different embodiments. For example, any of the embodiments claimed in the claims may be used in any combination.
Various component embodiments of the present disclosure may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. The present disclosure may also be implemented as an apparatus or system program (e.g., a computer program and a computer program product) for performing a portion or all of the methods described herein. Such a program embodying the present disclosure may be stored on a computer readable medium, or may have the form of one or more signals. Such signals may be downloaded from an internet website, provided on a carrier signal, or provided in any other form.
It should be noted that the above-mentioned embodiments illustrate rather than limit the disclosure, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The disclosure may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware.
The foregoing is merely a specific embodiment of the disclosure, and it should be noted that it will be apparent to those skilled in the art that various improvements, modifications, and variations can be made without departing from the spirit of the disclosure, and such improvements, modifications, and variations are considered to be within the scope of the application.
Claims (13)
1. A Zookeeper-based interface monitoring system, the system comprising:
the loading configuration unit is connected with the node management unit at one end; the loading configuration unit is used for loading a configuration file to obtain a configuration instruction and sending the configuration instruction to the node management unit;
the node management unit comprises a node operation module and a registration monitoring module; the node management unit adopts a Zookeeper framework;
the node operation module comprises 1 master node, M slave nodes and N load nodes; the M, N are all positive integers; the main node is used for sending a main node instruction and a main node heartbeat packet to the registration monitoring module according to the configuration instruction, and running a plug-in; the slave node is used for operating the plug-in unit according to the master node instruction, and judging whether to elect a new master node according to the master node heartbeat packet and a preset rule; the load node is used for sending a load distribution request to the registration monitoring module according to the main node instruction and a load algorithm;
one end of the registration monitoring module is connected with the node operation module and is used for sending the master node instruction to the slave node and the load node, sending the heartbeat packet of the master node to the slave node and sending the load distribution request to the master node and the slave node;
the interface monitoring unit is connected with the node management unit at one end; the interface monitoring unit is used for monitoring the conditions of all the interfaces.
2. The system according to claim 1, wherein:
the system comprises a web service access function which is constructed based on a Dropwizard framework, a dependency injection which is realized based on a guide framework and a tangent plane oriented function.
3. The system of claim 1, wherein the system further comprises:
the plug-in extension unit is connected with the node management unit at one end; the plug-in expansion unit is used for independently developing plug-ins and providing the plug-ins for the node management unit;
the system initialization unit is connected with the loading configuration unit, the node management unit and the plug-in extension unit; the system initialization unit is used for realizing the functions of initializing the system during starting, background periodic scheduling task, health degree checking and service managed.
4. The system according to claim 1, wherein:
the slave node is also used for sending a heartbeat packet of the slave node to the registration monitoring module; the registration monitoring module is further used for sending the heartbeat packet of the slave node to the master node; the master node is also used for judging whether the corresponding slave node operates normally or not according to the slave node heartbeat packet; and if the slave node is abnormally operated, removing the abnormal operation slave node information from the storage.
5. The system of claim 1, wherein the slave node determining whether to elect a new master node according to the master node heartbeat packet and a preset rule comprises:
the M slave nodes detect the heartbeat packet of the master node, and if the P slave nodes judge that the master node runs abnormally, the master node is selected from the M slave nodes and acts as the master node; wherein, P is more than or equal to 1 and less than or equal to M.
6. The system according to claim 1, wherein: the interface monitoring unit monitors the conditions of all interfaces by adopting a VUE framework.
7. The system of claim 1, wherein monitoring the condition of each interface comprises:
monitoring configuration of interface monitoring, interface authorization condition, interface calling condition, interface liveness and interface health state.
8. An interface monitoring method based on Zookeeper, which is characterized by comprising the following steps:
acquiring a configuration instruction;
according to the configuration instruction, the master node sends a master node heartbeat packet to the slave node, sends a master node instruction to the slave node and the load node, and operates the plug-in;
the slave node operates a plug-in according to the master node instruction, and judges whether to elect a new master node according to the master node heartbeat packet and a preset rule;
the load node sends a load distribution request to the master node and the slave node according to the master node instruction and a load algorithm;
the master node, the slave node and the load node are managed based on a Zookeeper;
the condition of each interface is monitored.
9. The method of claim 8, further comprising, prior to the obtaining the configuration instruction:
initializing a system;
the master node, the slave node, and the load node register based on a Zookeeper.
10. The method of claim 8, wherein the method further comprises:
the slave node sends a slave node heartbeat packet to the master node; the master node judges whether the corresponding slave node operates normally according to the slave node heartbeat packet; and if the slave node is abnormally operated, removing the abnormal operation slave node information from the storage.
11. The method according to claim 8, wherein:
the number of the master nodes is 1, the number of the slave nodes is M, and the number of the load nodes is N; the M, N are all positive integers; the slave nodes judge whether to elect a new master node according to the master node heartbeat packet and a preset rule, wherein if P slave nodes judge that the master node operates abnormally according to the master node heartbeat packet, the slave nodes elect the master node and act as the master node from M slave nodes; wherein, P is more than or equal to 1 and less than or equal to M.
12. The method according to claim 8, wherein: including the use of VUE frames to monitor the conditions of the interfaces.
13. The method of claim 8, wherein monitoring the condition of each interface comprises:
monitoring configuration of interface monitoring, interface authorization condition, interface calling condition, interface liveness and interface health state.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011459120.XA CN112671601B (en) | 2020-12-11 | 2020-12-11 | Interface monitoring system and method based on Zookeeper |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011459120.XA CN112671601B (en) | 2020-12-11 | 2020-12-11 | Interface monitoring system and method based on Zookeeper |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112671601A CN112671601A (en) | 2021-04-16 |
| CN112671601B true CN112671601B (en) | 2023-10-31 |
Family
ID=75405000
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011459120.XA Active CN112671601B (en) | 2020-12-11 | 2020-12-11 | Interface monitoring system and method based on Zookeeper |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112671601B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104539055A (en) * | 2015-01-07 | 2015-04-22 | 山东鲁能智能技术有限公司 | Electric system key equipment actualizing-one-prepared method and system based on network |
| WO2018094909A1 (en) * | 2016-11-28 | 2018-05-31 | 网宿科技股份有限公司 | Node connection method and distributed computing system |
| CN109005045A (en) * | 2017-06-06 | 2018-12-14 | 北京金山云网络技术有限公司 | Active and standby service system and host node fault recovery method |
| CN109347906A (en) * | 2018-08-30 | 2019-02-15 | 腾讯科技（深圳）有限公司 | A kind of data transmission method, device and server |
| WO2020001060A1 (en) * | 2018-06-30 | 2020-01-02 | 华为技术有限公司 | Member change method for distributed system, and distributed system |
| CN110912780A (en) * | 2019-12-13 | 2020-03-24 | 无锡华云数据技术服务有限公司 | High-availability cluster detection method, system and controlled terminal |
| EP3686739A1 (en) * | 2019-01-28 | 2020-07-29 | EMC IP Holding Company LLC | Method and system for enabling agentless backup and restore operations on a container orchestration platform |
-
2020
- 2020-12-11 CN CN202011459120.XA patent/CN112671601B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104539055A (en) * | 2015-01-07 | 2015-04-22 | 山东鲁能智能技术有限公司 | Electric system key equipment actualizing-one-prepared method and system based on network |
| WO2018094909A1 (en) * | 2016-11-28 | 2018-05-31 | 网宿科技股份有限公司 | Node connection method and distributed computing system |
| CN109005045A (en) * | 2017-06-06 | 2018-12-14 | 北京金山云网络技术有限公司 | Active and standby service system and host node fault recovery method |
| WO2020001060A1 (en) * | 2018-06-30 | 2020-01-02 | 华为技术有限公司 | Member change method for distributed system, and distributed system |
| CN109347906A (en) * | 2018-08-30 | 2019-02-15 | 腾讯科技（深圳）有限公司 | A kind of data transmission method, device and server |
| EP3686739A1 (en) * | 2019-01-28 | 2020-07-29 | EMC IP Holding Company LLC | Method and system for enabling agentless backup and restore operations on a container orchestration platform |
| CN110912780A (en) * | 2019-12-13 | 2020-03-24 | 无锡华云数据技术服务有限公司 | High-availability cluster detection method, system and controlled terminal |
Non-Patent Citations (1)
| Title |
|---|
| 微服务在大型设备监控管理系统中的应用探究;熊肖磊;韩雄飞;赵炯;周奇才;;现代机械(06);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112671601A (en) | 2021-04-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9753809B2 (en) | Crash management of host computing systems in a cluster | |
| US9015006B2 (en) | Automated enablement of performance data collection | |
| CN109471770B (en) | System management method and device | |
| US7979749B2 (en) | Method and infrastructure for detecting and/or servicing a failing/failed operating system instance | |
| US8424000B2 (en) | Providing application high availability in highly-available virtual machine environments | |
| US11140029B1 (en) | Server side filtering in hybrid cloud environments | |
| US9003239B2 (en) | Monitoring and resolving deadlocks, contention, runaway CPU and other virtual machine production issues | |
| US10175973B2 (en) | Microcode upgrade in a storage system | |
| CN104737134A (en) | System and method for operating system agnostic hardware validation | |
| US10848839B2 (en) | Out-of-band telemetry data collection | |
| US20140195853A1 (en) | Cloud management using a component health model | |
| US9436539B2 (en) | Synchronized debug information generation | |
| US20170212815A1 (en) | Virtualization substrate management device, virtualization substrate management system, virtualization substrate management method, and recording medium for recording virtualization substrate management program | |
| Di Sanzo et al. | Machine learning for achieving self-* properties and seamless execution of applications in the cloud | |
| CN112769634B (en) | Zookeeper-based laterally-expandable distributed system and development method | |
| CN112671601B (en) | Interface monitoring system and method based on Zookeeper | |
| CN110908644B (en) | Configuration method and device of state node, computer equipment and storage medium | |
| US20080216057A1 (en) | Recording medium storing monitoring program, monitoring method, and monitoring system | |
| CN102904946B (en) | Method and device for managing nodes in cluster | |
| CN114281353A (en) | Avoiding platform and service outages using deployment metadata | |
| JP2016018269A (en) | Information processing apparatus, information processing method, and program | |
| CN114968947A (en) | Fault file storage method and related device | |
| WO2018173698A1 (en) | Monitoring system, computer-readable storage medium, and monitoring method | |
| US20060230196A1 (en) | Monitoring system and method using system management interrupt | |
| JP7389877B2 (en) | Network optimal boot path 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 |