CN108390919A - A kind of message synchronization system and method for highly reliable two-node cluster hot backup - Google Patents
A kind of message synchronization system and method for highly reliable two-node cluster hot backup Download PDFInfo
- Publication number
- CN108390919A CN108390919A CN201810076665.9A CN201810076665A CN108390919A CN 108390919 A CN108390919 A CN 108390919A CN 201810076665 A CN201810076665 A CN 201810076665A CN 108390919 A CN108390919 A CN 108390919A
- Authority
- CN
- China
- Prior art keywords
- message
- server
- service
- node cluster
- hot backup
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 13
- 230000010076 replication Effects 0.000 claims abstract description 17
- 230000001360 synchronised effect Effects 0.000 claims description 27
- 230000002688 persistence Effects 0.000 claims description 9
- 238000009826 distribution Methods 0.000 claims description 5
- 238000012544 monitoring process Methods 0.000 claims description 4
- 238000003860 storage Methods 0.000 claims description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000011160 research Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000000739 chaotic effect Effects 0.000 description 1
- 238000005314 correlation function Methods 0.000 description 1
- 239000000686 essence Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 230000002045 lasting effect Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
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/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Hardware Redundancy (AREA)
Abstract
The invention discloses a kind of message synchronization system and methods for highly reliable two-node cluster hot backup, it is desirable to provide a kind of high message synchronization system and method for highly reliable two-node cluster hot backup of reliability.It includes two-server, wherein one is used as master server, another conduct is for server;It is characterized in that:Two server equal arrangements messaging bus Message Queues, two-node cluster hot backup management service APSB, data access layer service DataAdapter, database D B and isochronous queue Replication Queues.The present invention is used suitable for all kinds of enterprises.
Description
Technical field
The present invention relates to field of software engineering, more particularly, to a kind of message synchronization system for highly reliable two-node cluster hot backup
And method.
Background technology
Fame and economic loss will be brought to enterprise in the hang-up of field of software engineering, computer system, in order to
Avoid the risk that system-down is brought, enterprise can ensure the complete of business continuity and data by the way of two-node cluster hot backup.
Traditional computer system framework contains the message bus system of a set of two-node cluster hot backup and a set of application server.
The message bus system of two-node cluster hot backup uses the cluster management software that producer provides, and the messaging bus server of two physics is empty
Intend into a server, virtual server may be any one in two physical servers.What application server generated disappears
Breath is distributed to virtual server, and reception, distribution, persistence and the management by synchronization of message are completed by virtual server.
When message bus system breaks down, cluster management software will carry out active and standby cut between two physical servers
It changes.During active-standby switch, the business datum meeting partial loss that application server is generated gives enterprise so that business is interrupted
Production operation bring security risk.
Invention content
The purpose of the present invention is intended to overcome the shortcomings of the prior art, provide that a kind of data transmission stablizes for height
The message synchronization system and method for reliable two-node cluster hot backup.
In order to solve the above-mentioned technical problem, the present invention is achieved by the following technical solutions:
A kind of message synchronization system for highly reliable two-node cluster hot backup, including two-server, wherein one is used as master server,
Another conduct is for server;Two server equal arrangements messaging bus Message Queues, independent research it is double
The hot standby management service APSB of machine, independent research data access layer service DataAdapter, database D B and isochronous queue
Replication Queues;The messaging bus Message Queues are used to receive the message of producer's publication, and will disappear
Breath is distributed to each consumer for having subscribed the message;The APSB services are related to business on the machine messaging bus for subscribing to
Message, the consumer as service message;The APSB services while being responsible for prison and and receives on another server
Isochronous queue Replication Queues, and will be corresponding with message is received on the news release of reception to the machine messaging bus
In queue, while as the producer of service message;The data access layer service DataAdapter is for subscribing to the machine message
The message that persistence is needed in bus, the consumer of the message as persistence;The data access layer services DataAdapter
It is responsible for monitoring and receiving the message for needing perdurable data on messaging bus, is parsed after reception message, is stored in database D B
In;The database D B is for message duration, storage business datum;The isochronous queue Replication Queues are responsible for
Receive the message that need to be synchronized to another server and the two-node cluster hot backup pipe by these message distributions to another server
Reason service APSB.
Preferably, the isochronous queue Replication Queues be on same server one of messaging bus or
Multiple queues, or the application or service for realizing queue type data structure independently of messaging bus.
Preferably, the messaging bus Message Queues include but not limited to Apach ActiveMQ, IBM
WebSphere MQ、BEA Weblogic JMS Server、Oracle AQ、Tibco、Swift MQ。
Preferably, the database D B include but not limited to SQL Server, Oracle, DB2, PostgreSQL,
Access、My SQL。
A kind of message synchronization method of message synchronization system that realizing highly reliable two-node cluster hot backup as described above, feature exist
In:For message during being transmitted to destination server from source server, source server two-node cluster hot backup management service is in message
Synchronous mark is increased, to prevent message back to source server;It is as follows:
a)Business module issuing service message is to the messaging bus of source server, the two-node cluster hot backup management service sum number of source server
It is subscribed to according to access layer service and receives service message;The data access layer service of source server is deposited after parsing service message
Enter database;
b)The two-node cluster hot backup management service of source server is distributed to the machine after the service message received is increased synchronous mark
Isochronous queue;
c)The two-node cluster hot backup management service of destination server receives the message with synchronous mark in source server isochronous queue, and will
These service messages are distributed on the messaging bus of destination server;
d)The data Layer of destination server accesses service and two-node cluster hot backup management service receives the message with synchronous mark;Data
Access layer service is stored in database after parsing service message;Because band message has synchronous mark, the two-node cluster hot backup of destination server
Management service is not processed the message, directly abandons.
Preferably, the source server determines main service according to the start completion time of two-node cluster hot backup management service
Device, steps are as follows:
Step 1:The server of system start completion, two-node cluster hot backup management service elder generation start completion is master server, has been started afterwards
At being standby server;
Step 2:When certain server fail delay machine, the server of normal operation is master server;
Step 3:When an only server operation, which is master server.
Compared with prior art, the invention has the advantages that:
Present invention can ensure that during active/standby server switches, the business datum that application server is generated is not lost, and is avoided
The service disconnection caused by loss of data, the stability for enterprise's production operation provide safeguard.
Description of the drawings
In order to more clearly explain the embodiment of the invention or the technical proposal in the existing technology, to embodiment or will show below
There is attached drawing needed in technology description to be briefly described, it should be apparent that, the accompanying drawings in the following description is only this
Some embodiments of invention for those of ordinary skill in the art without creative efforts, can be with
Other attached drawings are obtained according to these attached drawings.
Fig. 1 is the system architecture figure of the present invention.
Fig. 2 is system architecture figure when service message is distributed to source server messaging bus.
Fig. 3 is the system architecture figure that APSB services and DataAdapter services receive service message.
Fig. 4 is the system architecture figure of the deposit source server database of service message.
Fig. 5 is the system architecture figure that service message enters source server isochronous queue.
Fig. 6 is the system architecture figure that service message is forwarded to destination server APSB.
Fig. 7 is the system architecture figure for the messaging bus that service message is forwarded to destination server.
Fig. 8 is the system architecture figure that APSB and DataAdapter receives service message on purpose server.
Fig. 9 is the system architecture figure of service message persistence on purpose server.
Figure 10 is the high end control system topological diagram of certain airdrome luggage in the specific embodiment of the invention.
Figure 11 is the framework map of server Dual-Computer Hot-Standby System used in Figure 10.
Specific implementation mode
Following will be combined with the drawings in the embodiments of the present invention, and technical solution in the embodiment of the present invention carries out clear, complete
Site preparation describes, it is clear that described embodiments are only a part of the embodiments of the present invention, instead of all the embodiments.It is based on
Embodiment in the present invention, those of ordinary skill in the art are obtained every other under the premise of not making the creative labor
Embodiment shall fall within the protection scope of the present invention.
In being described below, for the sake of clarity, some technical names will be described by the way of abbreviation, particularly will
Two-node cluster hot backup management service APSB is referred to as APSB services or APSB, and data access layer service DataAdapter is referred to as
DataAdapter is serviced or DataAdapter, remaining is used, and referred to as the rest may be inferred.
The message synchronization system of highly reliable two-node cluster hot backup is used for shown in Fig. 1, including two-server, wherein one is used as master
Server, another conduct is for server;Equal arrangement messaging bus Message Queues of two servers, two-node cluster hot backup
Management service APSB, data access layer service DataAdapter, database D B and isochronous queue Replication Queues;
The messaging bus Message Queues are used to receive the message of producer's publication, and message distribution is had subscribed the message
Each consumer;APSB service for subscribe on the machine messaging bus with the relevant message of business, as service message
Consumer;The APSB services while being responsible for prison and and receives the isochronous queue Replication on another server
Queues, and by the news release of reception to the machine messaging bus with receive in the corresponding queue of message, while as business
The producer of message;The data access layer service DataAdapter needs persistence for subscribing on the machine messaging bus
Message, the consumer of the message as persistence;The data access layer service DataAdapter is responsible for monitoring and receiving message
The message of perdurable data is needed in bus, is parsed, is stored in database D B after reception message;The database D B is used for
Message duration, storage business datum;The isochronous queue Replication Queues, which are responsible for receiving, need to be synchronized to other one
The message of a server and two-node cluster hot backup management service APSB by these message distributions to another server.
The isochronous queue Replication Queues are one or more queues on messaging bus, or independent
In the application or service of the realization queue type data structure of messaging bus.
The messaging bus Message Queues use the messaging bus product of the market mainstream, including but not limited to
Apach ActiveMQ、IBM WebSphere MQ、BEA Weblogic JMS Server、Oracle AQ、Tibco、Swift
MQ can also be the application or service with messaging bus correlation function of oneself exploitation, the limitation of no version.
The database D B can be used the database of any one mainstream, including but not limited to SQL Server, Oracle,
DB2, PostgreSQL, Access, My SQL, the limitation of no version.
A kind of message synchronization method of message synchronization system that realizing highly reliable two-node cluster hot backup as described above, feature exist
In:For message during being transmitted to destination server from source server, source server two-node cluster hot backup management service is in message
Synchronous mark is increased, to prevent message back to source server;It is as follows:
a)Business module issuing service message is to the messaging bus of source server, the two-node cluster hot backup management service sum number of source server
It is subscribed to according to access layer service and receives service message;The data access layer service of source server is deposited after parsing service message
Enter database;
b)The two-node cluster hot backup management service of source server is distributed to the machine after the service message received is increased synchronous mark
Isochronous queue;
c)The two-node cluster hot backup management service of destination server receives the message with synchronous mark in source server isochronous queue, and will
These service messages are distributed on the messaging bus of destination server;
d)The data Layer of destination server accesses service and two-node cluster hot backup management service receives the message with synchronous mark;Data
Access layer service is stored in database after parsing service message;Because band message has synchronous mark, the two-node cluster hot backup of destination server
Management service is not processed the message, directly abandons.
The switching of active/standby server is as follows:
(1)When system starts, the APSB services of two servers think that the host of oneself is master server.
(2)The start completion time is sent to the APSB of an other server by system start completion, APSB service timings
Service;The APSB services of an other server compare itself and the start completion time of oneself, if the startup of oneself is complete
At the time earlier than the time, oneself is switched to master server;If the start completion time of oneself is later than the time, by oneself
It is switched to standby server.
(3)When a server failure delay machine, trouble-free server is switched to master server.
(4)When an only server operation, the server of operation is master server.
(5)Master server is according to business logic processing business.
The detailed process of message synchronization method is as shown in figs 1-9, specific as follows:
(1)Some producer's (application or service) on source server Server1 generates a piece of news, and message is with BSM messages
For.The message is distributed to messaging bus Message Queues.As shown in Figure 2.
(2)APSB services and DataAdapter services on source server Server1 are all disappearing for BSM messages
Fei Zhe, therefore they can receive the BSM messages from messaging bus.As shown in Figure 3.
(3)DataAdapter services parsing BSM messages are simultaneously deposited into database D B, realize source server Server1
The persistence of upper message.As shown in Figure 4.
(4)Whether the APSB service inspections message on source server Server1 has synchronous mark, currently without increasing
Add a synchronous mark to BSM messages for ensuring that message will not be returned to from a server (destination server Server2)
Current server (source server Server1).BSM messages with synchronous mark are released to isochronous queue Replication
Queues, as shown in Figure 5.
(5)If APSB services receive the BSM messages from messaging bus Message Queues be with synchronous mark,
So, which will not all be distributed to isochronous queue, but can be simply discarded.
(6)The APSB services of another server (destination server Server2) receive the server (source server
Server1) the BSM messages in isochronous queue Replication Queues.As shown in Figure 6.
(7)The BSM messages with synchronous mark are distributed to destination server by APSB services on destination server Server2
The messaging bus Message Queues of Server2.As shown in Figure 7.
(8)APSB services and DataAdapter services on destination server Server2 receive BSM messages, because being somebody's turn to do
Message includes synchronous mark, and message can be serviced by APSB and directly be abandoned, to ensure that message does not return to source server
Server1.As shown in Figure 8.
(9)DataAdapter service parsing BSM messages on destination server Server2, and it is deposited into purpose service
In the database D B of device Server2, as shown in Figure 9.The step realizes that service message is lasting on destination server Server2
Change, also ensures that source server Server1 is synchronous with destination server Server2 data.From source server Server1 to purpose
Server S erver2 message synchronization processes, which take, is less than 1ms.When any one server delay machine is safeguarded, take over business
Server can obtain complete business datum by database D B.
(10)If message is generated, the data of Server2 to Server1 by certain producer's (application or service) of Server2
It is similar to synchronize flow flow synchronous with the data of Server1 to Server2.
Application Example:
In the high end control system of certain airport T3 terminal luggage, if we are come using traditional two-node cluster hot backup framework receiving
If from the flight data of airport backbone network Flight Information system when occur active/standby server switching, because part messages loss may
There can be flight data and receive incomplete situation, so that causing when sorting luggage chaotic.
We construct a set of highly reliable server Dual-Computer Hot-Standby System, which includes two server S erver1
And Server2.Network topological diagram is as shown in Figure 10.
Start server, Server1 and Server2 and determines that active/standby server, the service first started are according to boot sequence
Master server, the service started afterwards are standby server.Under normal conditions, first starting Server1, Server1 is master server,
Server2 is standby server.
In Server1 and Server2 equal arrangements messaging bus ActiveMQ, APSB service, data access layer service
It DataAdapter, database SQL Server, isochronous queue Replication Queues and is connect with Flight Information system
Mouth FISConnector services, isochronous queue Replication Queues are three created on messaging bus ActiveMQ
Queue.Server Dual-Computer Hot-Standby System framework is as shown in figure 11.
The foregoing is merely illustrative of the preferred embodiments of the present invention, is not intended to limit the invention, all essences in the present invention
With within principle, any modification, equivalent replacement, improvement and so on should all be included in the protection scope of the present invention god.
Claims (6)
1. a kind of message synchronization system for highly reliable two-node cluster hot backup, including two-server, wherein a main service of conduct
Device, another conduct is for server;It is characterized in that:Two server equal arrangements messaging bus Message
Queues, two-node cluster hot backup management service APSB, data access layer service DataAdapter, database D B and isochronous queue
Replication Queues;The messaging bus Message Queues are used to receive the message of producer's publication, and will disappear
Breath is distributed to each consumer for having subscribed the message;The APSB services are related to business on the machine messaging bus for subscribing to
Message, the consumer as service message;The APSB services while responsible monitoring simultaneously receive on another server
Isochronous queue Replication Queues, and will be corresponding with message is received on the news release of reception to the machine messaging bus
In queue, while as the producer of service message;The data access layer service DataAdapter is for subscribing to the machine message
The message that persistence is needed in bus, the consumer of the message as persistence;The data access layer services DataAdapter
It is responsible for monitoring and receiving the message for needing perdurable data on messaging bus, is parsed after reception message, is stored in database D B
In;The database D B is for message duration, storage business datum;The isochronous queue Replication Queues are responsible for
Receive the message that need to be synchronized to another server and the two-node cluster hot backup pipe by these message distributions to another server
Reason service APSB.
2. being used for the message synchronization system of highly reliable two-node cluster hot backup according to claim 1, it is characterised in that:The synchronous team
One or more queues that Replication Queues are messaging bus on same server are arranged, or total independently of message
The application or service of the realization queue type data structure of line.
3. being used for the message synchronization system of highly reliable two-node cluster hot backup according to claim 1, it is characterised in that:The message is total
Line Message Queues include but not limited to Apach ActiveMQ, IBM WebSphere MQ, BEA Weblogic JMS
Server、Oracle AQ、Tibco、Swift MQ。
4. being used for the message synchronization system of highly reliable two-node cluster hot backup according to claim 1, it is characterised in that:The database
DB includes but not limited to SQL Server, Oracle, DB2, PostgreSQL, Access, My SQL.
5. a kind of message synchronization side realizing the message synchronization system of highly reliable two-node cluster hot backup as described in claim 1-4 is any
Method, it is characterised in that:Message from source server during being transmitted to destination server, source server two-node cluster hot backup management clothes
Business increases synchronous mark in message, to prevent message back to source server;It is as follows:
a)Business module issuing service message is to the messaging bus of source server, the two-node cluster hot backup management service sum number of source server
It is subscribed to according to access layer service and receives service message;The data access layer service of source server is deposited after parsing service message
Enter database;
b)The two-node cluster hot backup management service of source server is distributed to the machine after the service message received is increased synchronous mark
Isochronous queue;
c)The two-node cluster hot backup management service of destination server receives the message with synchronous mark in source server isochronous queue, and will
These service messages are distributed on the messaging bus of destination server;
d)The data Layer of destination server accesses service and two-node cluster hot backup management service receives the message with synchronous mark;Data
Access layer service is stored in database after parsing service message;Because band message has synchronous mark, the two-node cluster hot backup of destination server
Management service is not processed the message, directly abandons.
6. the message synchronization method of the message synchronization system of highly reliable two-node cluster hot backup according to claim 5, it is characterised in that:
The server determines master server according to the start completion time of two-node cluster hot backup management service, and steps are as follows:
Step 1:The server of system start completion, two-node cluster hot backup management service elder generation start completion is master server, has been started afterwards
At being standby server;
Step 2:When certain server fail delay machine, the server of normal operation is master server;
Step 3:When an only server operation, which is master server.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810076665.9A CN108390919B (en) | 2018-01-26 | 2018-01-26 | Message synchronization system and method for high-reliability dual-computer hot standby |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810076665.9A CN108390919B (en) | 2018-01-26 | 2018-01-26 | Message synchronization system and method for high-reliability dual-computer hot standby |
Publications (2)
Publication Number | Publication Date |
---|---|
CN108390919A true CN108390919A (en) | 2018-08-10 |
CN108390919B CN108390919B (en) | 2021-06-25 |
Family
ID=63077476
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201810076665.9A Active CN108390919B (en) | 2018-01-26 | 2018-01-26 | Message synchronization system and method for high-reliability dual-computer hot standby |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN108390919B (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110333973A (en) * | 2018-12-28 | 2019-10-15 | 锐捷网络股份有限公司 | A kind of method and system of multi-host hot swap |
CN110958287A (en) * | 2018-09-27 | 2020-04-03 | 阿里巴巴集团控股有限公司 | Operation object data synchronization method, device and system |
CN111212100A (en) * | 2018-11-22 | 2020-05-29 | 财团法人工业技术研究院 | Synchronization method and system for publishing and subscribing message queue |
CN117033088A (en) * | 2023-08-17 | 2023-11-10 | 广东保伦电子股份有限公司 | Resource scheduling method and device suitable for dual-computer hot standby and server system |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6421688B1 (en) * | 1999-10-20 | 2002-07-16 | Parallel Computers Technology, Inc. | Method and apparatus for database fault tolerance with instant transaction replication using off-the-shelf database servers and low bandwidth networks |
CN201674530U (en) * | 2010-04-07 | 2010-12-15 | 上海交通大学医学院附属瑞金医院 | Addressing and treating device of disaster recovery server based on the FTP |
CN102111281A (en) * | 2009-12-24 | 2011-06-29 | 上海粱江通信系统股份有限公司 | Hot standby method for implementing dual-machine hot standby system |
CN102655460A (en) * | 2012-01-05 | 2012-09-05 | 中国工商银行股份有限公司 | Redundancy backup method and system of production server |
CN102833116A (en) * | 2012-09-07 | 2012-12-19 | 山西省电力公司电力科学研究院 | Electrical equipment state information fusing and showing system |
-
2018
- 2018-01-26 CN CN201810076665.9A patent/CN108390919B/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6421688B1 (en) * | 1999-10-20 | 2002-07-16 | Parallel Computers Technology, Inc. | Method and apparatus for database fault tolerance with instant transaction replication using off-the-shelf database servers and low bandwidth networks |
CN102111281A (en) * | 2009-12-24 | 2011-06-29 | 上海粱江通信系统股份有限公司 | Hot standby method for implementing dual-machine hot standby system |
CN201674530U (en) * | 2010-04-07 | 2010-12-15 | 上海交通大学医学院附属瑞金医院 | Addressing and treating device of disaster recovery server based on the FTP |
CN102655460A (en) * | 2012-01-05 | 2012-09-05 | 中国工商银行股份有限公司 | Redundancy backup method and system of production server |
CN102833116A (en) * | 2012-09-07 | 2012-12-19 | 山西省电力公司电力科学研究院 | Electrical equipment state information fusing and showing system |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110958287A (en) * | 2018-09-27 | 2020-04-03 | 阿里巴巴集团控股有限公司 | Operation object data synchronization method, device and system |
CN110958287B (en) * | 2018-09-27 | 2022-06-24 | 阿里云计算有限公司 | Operation object data synchronization method, device and system |
CN111212100A (en) * | 2018-11-22 | 2020-05-29 | 财团法人工业技术研究院 | Synchronization method and system for publishing and subscribing message queue |
CN111212100B (en) * | 2018-11-22 | 2022-07-19 | 财团法人工业技术研究院 | Synchronization method and system for publishing and subscribing message queue |
CN110333973A (en) * | 2018-12-28 | 2019-10-15 | 锐捷网络股份有限公司 | A kind of method and system of multi-host hot swap |
CN110333973B (en) * | 2018-12-28 | 2023-04-25 | 锐捷网络股份有限公司 | Multi-machine hot standby method and system |
CN117033088A (en) * | 2023-08-17 | 2023-11-10 | 广东保伦电子股份有限公司 | Resource scheduling method and device suitable for dual-computer hot standby and server system |
CN117033088B (en) * | 2023-08-17 | 2024-05-03 | 广东保伦电子股份有限公司 | Resource scheduling method and device suitable for dual-computer hot standby and server system |
Also Published As
Publication number | Publication date |
---|---|
CN108390919B (en) | 2021-06-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3490224B1 (en) | Data synchronization method and system | |
US10255343B2 (en) | Initialization protocol for a peer-to-peer replication environment | |
CN107590182B (en) | Distributed log collection method | |
US10965519B2 (en) | Exactly-once transaction semantics for fault tolerant FPGA based transaction systems | |
CN108390919A (en) | A kind of message synchronization system and method for highly reliable two-node cluster hot backup | |
US8903917B2 (en) | System and method for implementing a cluster token registry for business continuity | |
US20140108532A1 (en) | System and method for supporting guaranteed multi-point delivery in a distributed data grid | |
CN105630589A (en) | Distributed process scheduling system and process scheduling and execution method | |
US11068499B2 (en) | Method, device, and system for peer-to-peer data replication and method, device, and system for master node switching | |
CN105493474B (en) | System and method for supporting partition level logging for synchronizing data in a distributed data grid | |
JP2018504670A (en) | Message broker system with parallel persistence | |
CN103634411A (en) | Real-time market data broadcasting system and real-time market data broadcasting method with state consistency | |
KR20100099319A (en) | Node system, server switching method, server device, and data transfer method | |
WO2014135011A1 (en) | Database system and data synchronization method | |
CN107357800A (en) | A kind of database High Availabitity zero loses solution method | |
CN103605616A (en) | Multi-controller cache data consistency guarantee method | |
CN113127499B (en) | Block chain-based micro-service method, equipment and medium | |
CN110213359A (en) | A kind of car networking networking data delivery system and method based on D2D | |
US7748010B1 (en) | Global attribute uniqueness (GAU) using an ordered message service (OMS) | |
CN114598593A (en) | Message processing method, system, computing device and computer storage medium | |
CN113641511B (en) | Message communication method and device | |
WO2023280127A1 (en) | Message communication method and apparatus | |
CN117827544B (en) | Hot backup system, method, electronic device and storage medium | |
CN114116277A (en) | InfluxDB high-availability cluster implementation system and method | |
CN115665276A (en) | Service providing method and device |
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 | ||
CP03 | Change of name, title or address |
Address after: 650000 Room 205, Building 805, Kunchuan Industrial Zone, Kunchuan Community, Ala Sub district Office, Kunming Economic Development Zone, China (Yunnan) Pilot Free Trade Zone, Kunming City, Yunnan Province Patentee after: Kunming Kunchuan Smart Airport Technology Co.,Ltd. Address before: 650236 room 209, 401 building, Kunming Shipbuilding Industrial Zone, 8km east suburb, Kunming City, Yunnan Province Patentee before: KUNMING LOGAN-KSEC AIRPORT LOGISTICS SYSTEM Co.,Ltd. |
|
CP03 | Change of name, title or address |