CN109286525B - Double-computer backup method based on MQTT communication and heartbeat between main and standby - Google Patents

Double-computer backup method based on MQTT communication and heartbeat between main and standby Download PDF

Info

Publication number
CN109286525B
CN109286525B CN201811135172.4A CN201811135172A CN109286525B CN 109286525 B CN109286525 B CN 109286525B CN 201811135172 A CN201811135172 A CN 201811135172A CN 109286525 B CN109286525 B CN 109286525B
Authority
CN
China
Prior art keywords
node
message
heartbeat
condition monitoring
fault
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
Application number
CN201811135172.4A
Other languages
Chinese (zh)
Other versions
CN109286525A (en
Inventor
刘毅
杨映春
刘子龙
张�浩
师智良
张宇
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Kunming Enersun Technology Co Ltd
Original Assignee
Kunming Enersun Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Kunming Enersun Technology Co Ltd filed Critical Kunming Enersun Technology Co Ltd
Priority to CN201811135172.4A priority Critical patent/CN109286525B/en
Publication of CN109286525A publication Critical patent/CN109286525A/en
Application granted granted Critical
Publication of CN109286525B publication Critical patent/CN109286525B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
    • 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/0677—Localisation of faults
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Hardware Redundancy (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The invention discloses a double-computer backup method based on MQTT communication and heartbeat between a main computer and a standby computer, which aims to overcome the defects that in a double-computer backup scene, the Split-brain phenomenon occurs because the heartbeat mechanism between the main computer (a main node A, active) and the standby computer (a slave node B, standby) is only relied on to misjudge the state of the main computer, and the node self fault or the channel connection fault cannot be quickly positioned when the fault occurs. The message publishing/subscribing mechanism and the will advice mechanism of the MQTT are applied to a dual-computer mutual-standby scene and are used in a fusion mode with the inter-AB heartbeat line mechanism. The present invention enables A, B to monitor each other through publish/subscribe status monitoring messages and will messages. When the node A is abnormal, the node B immediately takes over the resources and services of the node A, and the defect that the split brain phenomenon occurs because the heartbeat mechanism between the nodes AB is only used for misjudging the state of the host is overcome. By fusing the message publishing/subscribing mechanism and the will advice mechanism of the MQTT with the AB-interval heartbeat line mechanism, the node fault or the channel fault can be quickly positioned according to the AB-interval heartbeat information, the MQTTD monitoring message and the will advice message.

Description

Double-computer backup method based on MQTT communication and heartbeat between main and standby
Technical Field
The invention belongs to a double-computer backup method relating to MQTT communication and heartbeat between a main computer and a standby computer in computer application.
Technical Field
The dual-machine backup mechanism is the most basic implementation manner in a high-availability cluster, and is used for constructing a service system with high reliability and high availability. In the prior art, communication between nodes in a dual-machine backup mechanism is implemented by heartbeat. The heartbeat monitoring can be carried out through a network link and a serial port, messages are mutually sent between the network link and the serial port to tell the current state of the opposite side, if the messages sent by the opposite side are not received in the appointed time, the opposite side is considered to be invalid, and at the moment, a resource taking-over module is required to be started to take over resources or services running on a host of the opposite side. The main and standby heartbeat mechanisms have the following problems: when the AB heart line fails and the node A is normal, the standby node B considers that the host node A fails and takes over the resources and services of the node A. However, in the actual situation, the node a does not have a fault, and at this time, the node B needs to take over the resources and services of the node a, and the node a still occupies the resources and provides the services, which causes a Split-brain (Split-brain) phenomenon. Split-bridge causes service anomalies, operational confusion, and data incompleteness.
The message queue Telemetry transmission MQTT (message Queuing technical transport) protocol provides network connection by using TCP/IP, provides one-to-many message publishing by adopting a publishing/subscribing message mode and releases application program coupling; and (5) processing abnormal disconnection by adopting a testament mechanism. The method comprises the steps that a Will Message (Will Message) is predefined by a client and stored in a server, when the client is abnormally disconnected, the server actively issues the Will Message to a Will Topic theme to inform a Will Topic relevant subscriber, and the client quits due to abnormality.
Disclosure of Invention
The present invention aims to overcome the defects of the prior art and provide a dual-computer backup method based on MQTT communication and heartbeat between a main computer and a standby computer.
The purpose of the invention is realized by the following technical scheme:
the invention relates to a double-machine backup method based on MQTT communication and heartbeat between a main machine and a standby machine, which is characterized in that an MQTT client A, B node is subjected to double-machine backup, wherein A is host equipment, B is standby equipment, for example, 1A and 1B are mutually backed up, 2A and 2B are mutually backed up, 2A and 3B are mutually backed up, and the like; and an AB heartbeat jumper wire is arranged between the node A and the node B to keep heartbeat connection. Monitoring each other;
the node A is a main device and normally provides specified service resources and functional services. The node B is a slave device, is used as a standby machine of the node A, is normally in a standby state, and takes over resources and services when the node A cannot provide specified service resources and functional services;
the node A is a main device and normally provides specified service resources and functional services; the Node A regularly issues related information Node A condition monitoring Message of a condition monitoring subject Node A condition monitoring Topic, and configures a testament Topic Node A wild Topic and a testament Message Node A wild Message; b Node subscribes Node A condition monitoring Topic and Will Topic Node A wild Topic, receives Node A condition monitoring Message and abnormal Will Message when Node A runs normally; the node B monitors the working state of the node A and the connectivity of the channel A through the state monitoring message and the advice message;
the node B is a slave device, is used as a standby machine of the node A, is normally in a standby state, and takes over resources and services when the node A cannot provide specified service resources and functional services; the Node B regularly releases the related information Node B condition monitoring Message of the condition monitoring subject Node B condition monitoring Message in the normal state, and configures the subject of the testament Node B Will Topic and the testament Message Node B Will Message; a Node subscribes a Node B condition monitoring Topic Node B condition monitoring Message and a testament Topic Node B Will Topic, and receives a condition monitoring Message Node B condition monitoring Message and a testament Message Node B Will Message when the Node B operates normally; the node A monitors the working state of the node B and the connectivity of a channel B through the state monitoring message and the advice message;
when the Node B can not receive the Node A condition monitoring Message and receives the Node A wild Message, the Node B takes over the resource and service of the Node B immediately; and issues a heartbeat state Message AB keep alive Message corresponding to the AB heartbeat Topic AB keep alive Topic to the server,
the operation and maintenance service locates the fault according to AB heartbeat information AB keep alive Message, Node A condition monitoring Message of the Node A and Node A wild Message;
if the AB keep alive Message shows that the Node A has no heartbeat and receives the Node A wild Message; or the AB keep alive Message shows that the Node A has no heartbeat, but does not receive the Node A condition monitoring Message and the Node A wild Message, the possibility of the Node A fault is judged to be maximum, and the fault is checked from the Node A;
if the AB keep alive Message shows that the Node A has a heartbeat and receives the Node A wild Message; or if the AB keep alive Message shows that the Node A has a heartbeat but does not receive the Node A condition monitoring Message and the Node A wild Message, judging that the possibility of the A channel fault is maximum, and troubleshooting the fault from the A channel;
when the Node A cannot receive the Node B condition monitoring Message and receives the Node B wild Message, a Node B fault warning Message is issued to remind the backup machine of repairing the abnormity as soon as possible; and issuing a heartbeat state Message AB keep alive Message corresponding to the AB heartbeat theme AB keep alive Topic to a server;
the operation and maintenance service locates the fault according to AB heartbeat information AB keep alive Message, Node A condition monitoring Message of the Node B and Node B wild Message;
if the AB keep alive Message shows that the heartbeat of the Node B does not exist, and the Node B wild Message is received; or the AB keep alive Message shows that the heartbeat of the Node B does not exist, but the Node B condition monitoring Message and the Node B wild Message are not received, the possibility of the Node A fault is judged to be maximum, and the fault is checked from the Node B;
if the AB keep alive Message shows that the heartbeat of the Node B exists and the Node B wild Message is received; or the AB keep alive Message shows that the heartbeat of the Node B exists, but the Node B condition monitoring Message and the Node B wild Message are not received, the possibility of the A channel fault is judged to be maximum, and the fault is checked from the B channel.
The invention has the beneficial effects that:
1. the message publishing/subscribing mechanism and the will-order mechanism of the MQTT are applied to a dual-computer mutual standby scene, and A, B dual computers are mutually monitored through publishing/subscribing state monitoring messages and will-order messages. When the host A is abnormal, the standby computer B immediately takes over the resources and services of the host, and the split brain phenomenon caused by misjudging the state of the host only by means of the inter-AB heartbeat mechanism is avoided. When the standby machine is abnormal, the host machine issues an alarm and reminds the user to repair as soon as possible.
2. The message publishing/subscribing mechanism and the will ordering mechanism of the MQTT are used in a fusion mode with the AB heartbeat line mechanism, and the problem that when a fault occurs, the node fault or the channel connection fault cannot be quickly positioned by independently depending on the AB heartbeat mechanism or the message publishing/subscribing mechanism and the will ordering mechanism of the MQTT to confirm the state is solved.
Drawings
Fig. 1 is a schematic diagram of a network topology between a master node, a slave node and an MQTT server according to the present invention.
Detailed Description
Referring to fig. 1, the invention discloses a dual-computer backup method based on MQTT communication and heartbeat between a main and a standby, which is characterized in that an MQTT client A, B node is subjected to dual-computer backup, wherein a is a host device and B is a standby device, for example, 1A and 1B are backed up with each other, 2A and 2B are backed up with each other, 2A and 3B are backed up with each other, and the like; and an AB heartbeat jumper wire is arranged between the node A and the node B to keep heartbeat connection. Monitoring each other;
the node A is a main device and normally provides specified service resources and functional services. The node B is a slave device, is used as a standby machine of the node A, is normally in a standby state, and takes over resources and services when the node A cannot provide specified service resources and functional services;
the node A is a main device and normally provides specified service resources and functional services; the Node A regularly issues related information Node A condition monitoring Message of a condition monitoring subject Node A condition monitoring Topic, and configures a testament Topic Node A wild Topic and a testament Message Node A wild Message; b Node subscribes Node A condition monitoring Topic and Will Topic Node A wild Topic, receives Node A condition monitoring Message and abnormal Will Message when Node A runs normally; the node B monitors the working state of the node A and the connectivity of the channel A through the state monitoring message and the advice message;
the node B is a slave device, is used as a standby machine of the node A, is normally in a standby state, and takes over resources and services when the node A cannot provide specified service resources and functional services; the Node B regularly releases the related information Node B condition monitoring Message of the condition monitoring subject Node B condition monitoring Message in the normal state, and configures the subject of the testament Node B Will Topic and the testament Message Node B Will Message; a Node subscribes a Node B condition monitoring Topic Node B condition monitoring Message and a testament Topic Node B Will Topic, and receives a condition monitoring Message Node B condition monitoring Message and a testament Message Node B Will Message when the Node B operates normally; the node A monitors the working state of the node B and the connectivity of a channel B through the state monitoring message and the advice message;
when the Node B can not receive the Node A condition monitoring Message and receives the Node A wild Message, the Node B takes over the resource and service of the Node B immediately; and issues a heartbeat state Message AB keep alive Message corresponding to the AB heartbeat Topic AB keep alive Topic to the server,
the operation and maintenance service locates the fault according to AB heartbeat information AB keep alive Message, Node A condition monitoring Message of the Node A and Node A wild Message;
if the AB keep alive Message shows that the Node A has no heartbeat and receives the Node A wild Message; or the AB keep alive Message shows that the Node A has no heartbeat, but does not receive the Node A condition monitoring Message and the Node A wild Message, the possibility of the Node A fault is judged to be maximum, and the fault is checked from the Node A;
if the AB keep alive Message shows that the Node A has a heartbeat and receives the Node A wild Message; or if the AB keep alive Message shows that the Node A has a heartbeat but does not receive the Node A condition monitoring Message and the Node A wild Message, judging that the possibility of the A channel fault is maximum, and troubleshooting the fault from the A channel;
when the Node A cannot receive the Node B condition monitoring Message and receives the Node B wild Message, a Node B fault warning Message is issued to remind the backup machine of repairing the abnormity as soon as possible; and issuing a heartbeat state Message AB keep alive Message corresponding to the AB heartbeat theme AB keep alive Topic to a server;
the operation and maintenance service locates the fault according to AB heartbeat information AB keep alive Message, Node A condition monitoring Message of the Node B and Node B wild Message;
if the AB keep alive Message shows that the heartbeat of the Node B does not exist, and the Node B wild Message is received; or the AB keep alive Message shows that the heartbeat of the Node B does not exist, but the Node B condition monitoring Message and the Node B wild Message are not received, the possibility of the Node A fault is judged to be maximum, and the fault is checked from the Node B;
if the AB keep alive Message shows that the heartbeat of the Node B exists and the Node B wild Message is received; or the AB keep alive Message shows that the heartbeat of the Node B exists, but the Node B condition monitoring Message and the Node B wild Message are not received, the possibility of the A channel fault is judged to be maximum, and the fault is checked from the B channel.
The state monitoring message and heartbeat message service condition analysis under different situations is as follows:
scenario 1: if the Node A has a fault, the Node B cannot subscribe to the Node A condition monitoring Message of the Node A through the MQTT, and cannot monitor the heartbeat of the Node A through the AB heartbeat line. And vice versa.
Scenario 2: if the A channel has a fault, the Node B can not subscribe the status Node A conditioning monitoring Message of the Node A through the MQTT, and the heartbeat of the Node A can be monitored through the AB heartbeat line. And vice versa.
Scenario 3: if the AB heartbeat line fails, the Node B can subscribe to the Node A condition monitoring Message of the Node A through the MQTT, and the heartbeat of the Node A cannot be monitored through the AB heartbeat line. And vice versa.
Scenario 4: and if the Node, the channel and the AB heartbeat line are normal, the Node B can subscribe to the Node A condition monitoring Message of the Node A through the MQTT, and the Node A heartbeat is monitored through the AB heartbeat line. And the node A can monitor the node similarly.
State monitoring message and heartbeat message service condition table under different situations
Figure BDA0001814496460000051
And mutually publishing/subscribing the state monitoring information and the advice information through MQTT, and taking over the resources and services of the node A when the node B cannot receive the state monitoring information of the node A. The problem that due to AB heartbeat line faults, resources and services of the node A are taken over under the normal state of the node A and the channel A is avoided, and the split brain problem in the case of the scenario 3 is avoided.
Through the mutual publishing/subscribing of the state monitoring information by the AB heartbeat line and the MQTT, the problem that the node self fault or the channel connection fault cannot be quickly positioned when the state is confirmed by independently depending on the AB heartbeat line is solved.

Claims (1)

1. A double-machine backup method based on MQTT communication and heartbeat between a main node and a standby node is characterized in that an MQTT client A, B node is subjected to double-machine backup, wherein a node A is host equipment, a node B is standby equipment, a node 1A and a node 1B are mutually backed up, a node 2A and a node 2B are mutually backed up, a node 3A and a node 3B are mutually backed up, and the rest is done in the same way; an AB heartbeat jumper wire is arranged between the node A and the node B, and heartbeat connection is kept and mutual monitoring is carried out;
the node A is a main device and normally provides specified service resources and functional services; the node B is a slave device, is used as a standby machine of the node A and is normally in a standby state, and takes over the service resources and the function services when the node A can not provide the specified service resources and the function services;
the Node A is a main device, the Node A regularly releases a state monitoring subject in a normal state, wherein the state monitoring subject comprises a Node A condition monitoring Message and a Node A condition monitoring Message, and the Node A condition monitoring Message is a Node A condition monitoring Message;
b Node subscribes Node A condition monitoring Topic and Will Topic Node A wild Topic, receives Node A condition monitoring Message and abnormal Will Message when Node A runs normally;
the node B monitors the working state of the node A and the connectivity of the channel A through the state monitoring message and the advice message;
the Node B is slave equipment, the Node B normal state regularly issues a state monitoring subject, namely a Node B condition monitoring Message, and configures a testament subject, namely a Node B Will Message and a testament Message;
a Node subscribes a Node B condition monitoring Topic Node B condition monitoring Message and a testament Topic Node B Will Topic, and receives a condition monitoring Message Node B condition monitoring Message and a testament Message Node B Will Message when the Node B operates normally;
the node A monitors the working state of the node B and the connectivity of a channel B through the state monitoring message and the advice message;
when the Node B can not receive the Node A condition monitoring Message and receives the Node A wild Message, the Node B takes over the service resource and the function service of the Node A immediately and plays the role of a standby machine; and issues AB heartbeat subject, AB keep alive Message corresponding to the heartbeat state Message AB keep alive Message to the server,
the operation and maintenance service locates the fault according to the AB heartbeat state Message AB keep alive Message, the Node A condition monitoring Message of the Node A and the Node A wild Message;
if the AB keep alive Message shows that the Node A has no heartbeat and receives the Node A wild Message; or the AB keep alive Message shows that the Node A has no heartbeat but does not receive the Node A condition monitoring Message and the Node A wild Message, the possibility of the Node A fault is judged to be maximum, and the fault is checked from the Node A;
if the AB keep alive Message shows that the Node A has heartbeat and receives the Node A wild Message; or if the AB keep alive Message shows that the Node A has heartbeat but does not receive the Node A condition monitoring Message and the Node A wild Message, judging that the possibility of the A channel fault is maximum, and starting to troubleshoot the fault from the A channel;
when the Node A cannot receive the Node B condition monitoring Message and receives the Node B wild Message, a Node B fault alarm Message is issued to remind the standby machine of repairing the abnormity as soon as possible; and issuing AB heartbeat subject, namely a heartbeat state Message corresponding to AB keep alive Topic, wherein the AB keep alive Message is sent to a server;
the operation and maintenance service locates the fault according to the AB heartbeat state Message AB keep alive Message, the Node B condition monitoring Message of the Node B and the Node B wild Message;
if the AB keep alive Message shows that the heartbeat of the Node B does not exist, and the Node B wild Message is received; or the AB keep alive Message shows that no Node B has heartbeat but does not receive the Node B condition monitoring Message and the Node B wild Message, the possibility of the Node B fault is judged to be maximum, and the fault is checked from the Node B;
if the AB keep alive Message shows that the heartbeat of the Node B exists and the Node B wild Message is received; or the AB keep alive Message shows that the heartbeat of the Node B exists, but the Node B condition monitoring Message and the Node B wild Message are not received, the possibility of the B channel fault is judged to be maximum, and the fault is checked from the B channel.
CN201811135172.4A 2018-09-28 2018-09-28 Double-computer backup method based on MQTT communication and heartbeat between main and standby Active CN109286525B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201811135172.4A CN109286525B (en) 2018-09-28 2018-09-28 Double-computer backup method based on MQTT communication and heartbeat between main and standby

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201811135172.4A CN109286525B (en) 2018-09-28 2018-09-28 Double-computer backup method based on MQTT communication and heartbeat between main and standby

Publications (2)

Publication Number Publication Date
CN109286525A CN109286525A (en) 2019-01-29
CN109286525B true CN109286525B (en) 2022-02-25

Family

ID=65182250

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201811135172.4A Active CN109286525B (en) 2018-09-28 2018-09-28 Double-computer backup method based on MQTT communication and heartbeat between main and standby

Country Status (1)

Country Link
CN (1) CN109286525B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110278248B (en) * 2019-05-29 2022-04-22 平安科技（深圳）有限公司 Method and device for distributing testament information and computer readable storage medium
CN110166487B (en) * 2019-06-19 2022-04-19 深圳聚点互动科技有限公司 Local area network equipment information transmission method, main equipment, storage medium and intelligent equipment
CN110515776B (en) * 2019-08-30 2023-01-31 南京图格医疗科技有限公司 Dual-computer backup system and backup method

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102799394A (en) * 2012-06-29 2012-11-28 华为技术有限公司 Method and device for realizing heartbeat services of high-availability clusters
CN107181792A (en) * 2017-04-21 2017-09-19 珠海派诺科技股份有限公司 Remote equipment management method and device based on MQTT and n2n VPN
CN107819642A (en) * 2017-09-15 2018-03-20 中国科学院计算技术研究所 Based on distributed adaptive heartbeat method and system
CN108540367A (en) * 2017-03-06 2018-09-14 中国移动通信有限公司研究院 A kind of message treatment method and system

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10904111B2 (en) * 2014-10-02 2021-01-26 International Business Machines Corporation Lightweight framework with dynamic self-organizing coordination capability for clustered applications
CN107634855A (en) * 2017-09-12 2018-01-26 天津津航计算技术研究所 A kind of double hot standby method of embedded system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102799394A (en) * 2012-06-29 2012-11-28 华为技术有限公司 Method and device for realizing heartbeat services of high-availability clusters
CN108540367A (en) * 2017-03-06 2018-09-14 中国移动通信有限公司研究院 A kind of message treatment method and system
CN107181792A (en) * 2017-04-21 2017-09-19 珠海派诺科技股份有限公司 Remote equipment management method and device based on MQTT and n2n VPN
CN107819642A (en) * 2017-09-15 2018-03-20 中国科学院计算技术研究所 Based on distributed adaptive heartbeat method and system

Also Published As

Publication number Publication date
CN109286525A (en) 2019-01-29

Similar Documents

Publication Publication Date Title
CN109286525B (en) Double-computer backup method based on MQTT communication and heartbeat between main and standby
CN101083698B (en) Monitoring apparatus
US8174962B2 (en) Global broadcast communication system
JPH03106144A (en) Mutual connection of network modules
EP2776928A1 (en) Systems and methods for automatic replacement and repair of communications network devices
JP2013130901A (en) Monitoring server and network device recovery system using the same
CN103810076A (en) Monitoring method and device for data reproduction
JP4544415B2 (en) Relay network system, node device, and failure notification method
CN102801578B (en) A kind of supervisory control system of transaction platform
CN104796283A (en) Monitoring alarm method
KR101216682B1 (en) Smart access redundancy network system in network
US9323629B2 (en) Method for managing path failures of OSEK networks
CN108234154B (en) Airborne switching network equipment fault monitoring method
CN102185720A (en) North notification management interface device and management method thereof
CN113708967B (en) System monitoring disaster recovery early warning device and early warning method
KR100832543B1 (en) High availability cluster system having hierarchical multiple backup structure and method performing high availability using the same
JP5005425B2 (en) Control device return system
CN109510725B (en) Communication equipment fault detection system and method
JP4026606B2 (en) Uninterruptible power supply management system
JP4863984B2 (en) Monitoring processing program, method and apparatus
CN107302452B (en) Control method for PBX service continuity
JP2014110620A (en) Network operation system
JP5172186B2 (en) Security system
US20140297724A1 (en) Network element monitoring system and server
JP2006319683A (en) System and apparatus for monitoring network 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