CN110855505A - High-availability rule stacking implementation system and method - Google Patents
High-availability rule stacking implementation system and method Download PDFInfo
- Publication number
- CN110855505A CN110855505A CN201911175790.6A CN201911175790A CN110855505A CN 110855505 A CN110855505 A CN 110855505A CN 201911175790 A CN201911175790 A CN 201911175790A CN 110855505 A CN110855505 A CN 110855505A
- Authority
- CN
- China
- Prior art keywords
- node
- rule
- node group
- configuring
- nodes
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- 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
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Hardware Redundancy (AREA)
Abstract
The invention discloses a high-availability rule stacking realization system and a method thereof, wherein the method comprises the following steps: step S1, configuring each working machine as a working node, dividing all the working nodes into a plurality of node groups, wherein each node group comprises two nodes, configuring the nodes of each node group as a main node and a slave node, configuring high availability rules for each node group, configuring a virtual IP for each rule, and adding a heartbeat wire; step S2, regarding each node group as a whole as a node, dividing the node group into a plurality of father node groups again, wherein each original node group is called as a child node group of the corresponding father node group, configuring the nodes of each father node group as a main node and a slave node, configuring high-availability rules for each father node group, configuring a virtual IP for each rule, and setting a heartbeat line; and step S3, taking each father node group as a child node group, returning to step S2, and stacking the high availability rules again until the last father node group.
Description
Technical Field
The invention relates to the technical field of computer data backup disaster recovery, in particular to a high-availability rule stacking implementation system and method based on high availability.
Background
Today, the enterprise informatization process is accelerating, each enterprise starts to build an information system, and the maintenance of the continuity of the business is an important aspect which must be considered when enterprise users perform data processing, so that each enterprise pays more and more attention to the aspects of data backup and safety, information is important to each enterprise or individual, and information safety becomes a problem worthy of research in the field of computer disaster tolerance at present.
However, in work and life, it often happens that a computer cannot work for various reasons, and if such a situation occurs in an enterprise, it is likely to cause unnecessary loss to the enterprise, so a High Availability (HA) rule is required to shorten the downtime of the computer due to an emergency situation, so that the computer can continuously provide services.
High availability generally refers to the realization of continuity of service by design to reduce the time during which the system is unable to provide service. Fig. 1 is a high availability operational diagram. The high availability of the application mainly aims at providing high availability service for various applications, multiple high availability rules can be provided for protection during monitoring, a monitoring object can be a main node, a slave node or simultaneous monitoring, an arbitration mechanism is introduced, error switching and the like of the main node and the slave node due to network and the like are avoided, data are synchronously added into the high availability, and the high availability of data synchronization association is realized. When the service monitored by the master node or the process and the like have faults, the master node becomes a slave node, the association replication rule from the original master node to the original slave node is stopped, the slave node is switched to the master node, and the association replication rule from the new master node to the new slave node is started.
When the host works normally and the monitoring object does not have abnormal appearance, the host provides services to the outside, changed data is copied to the slave node in real time through the association rule, and the monitoring object configured by the high-availability rule keeps a real-time monitoring state; when the monitoring object is in an abnormal state, executing a resource switching script, stopping the association rule, and switching the main node into a slave node; and migrating the virtual IP address to the slave node, starting the service by the slave node, starting the association rule, jumping to the master node by the slave node at the moment, and continuously providing the service to the outside.
Although the high availability may be realized by switching the slave node to the master node to continue providing the service to the outside when the service monitored by the master node or the process fails, when the slave node also fails, a system abnormality may still be caused, and the service cannot be continuously provided, thereby causing unnecessary loss.
Disclosure of Invention
In order to overcome the above-mentioned deficiencies of the prior art, the present invention provides a high availability rule stacking system and method, so as to form a high availability service of an outermost HA master-slave node to protect data by stacking a plurality of HAs, thereby more effectively reducing the downtime caused by downtime and maintaining the high availability of the service.
To achieve the above object, the present invention provides a high-availability rule stack implementation system, including:
the initial node configuration unit is used for configuring each working machine as a working node, dividing all the working nodes into a plurality of node groups, wherein each node group comprises two nodes, and configuring the nodes of each node group as a master node and a slave node;
the high-availability rule configuration unit is used for configuring high-availability rules for each node group, configuring a virtual IP for each rule and adding a heartbeat line;
and the stacking unit is used for regarding each node group of the lower level as a whole as a node layer by layer, dividing a plurality of father node groups, configuring the nodes of each father node group into a main node and a slave node, configuring a high availability rule for each father node group by using the high availability rule configuration unit, configuring a virtual IP for each rule, and setting a heartbeat line until the last father node group so as to realize high availability rule stacking.
Preferably, the regular heartbeat line of each parent node group uses the virtual IP and network card of each node as connection.
Preferably, the virtual IP of each rule is added on the corresponding master node.
Preferably, each high-availability rule of the bottom layer carries high-availability service information of a rule stacked by the corresponding stacking unit.
In order to achieve the above object, the present invention further provides a method for implementing high-availability rule stacking, including the following steps:
step S1, configuring each working machine as a working node, dividing all the working nodes into a plurality of node groups, wherein each node group comprises two nodes, configuring the nodes of each node group as a main node and a slave node, configuring high availability rules for each node group, configuring a virtual IP for each rule, and adding a heartbeat wire;
step S2, regarding each node group as a whole as a node, dividing the node group into a plurality of father node groups again, wherein each original node group is called as a child node group of the corresponding father node group, configuring the nodes of each father node group as a main node and a slave node, configuring high-availability rules for each father node group, configuring a virtual IP for each rule, and setting a heartbeat line;
and step S3, taking each father node group as a child node group, returning to step S2, and stacking the high availability rules again until the last father node group.
Preferably, in step S1, all the master nodes of the rule carry the highly available service of the highly available rule, and synchronize some data information of the highly available rule to the corresponding slave nodes through the associated replication rule.
Preferably, each regular virtual IP is added on a respective master node.
Preferably, in step S2, the rule-based core jumper of each parent node group uses the virtual IP and the network card of each node rule as a connection.
Compared with the prior art, the high-availability rule stacking system and the method realize the stacking of the high-availability rules by configuring each working machine as the working nodes, dividing all the working nodes into a plurality of node groups, configuring the nodes of each node group as a main node and a slave node, configuring the high-availability rules for each node group, configuring a virtual IP for each rule, adding a heartbeat line, regarding each node group at the lower level as a whole as a node layer by layer, dividing a plurality of father node groups, configuring the nodes of each father node group as a main node and a slave node, configuring the high-availability rules for each father node group by using the high-availability rule configuration unit, configuring a virtual IP for each rule, and setting the heartbeat line until the last father node group, so that a large batch of machines can still continuously provide services when crashes occur, the downtime is shortened.
Drawings
FIG. 1 is a high availability operational schematic;
FIG. 2 is a system architecture diagram of a high availability rule stack implementation system of the present invention;
FIG. 3 is a diagram illustrating an example of a high availability rule stack in accordance with an embodiment of the present invention;
FIG. 4 is a flow chart of the steps of a high availability rule stack implementation method of the present invention;
FIG. 5 is a schematic diagram of the operation of the high availability rule stack of the present invention.
Detailed Description
Other advantages and capabilities of the present invention will be readily apparent to those skilled in the art from the present disclosure by describing the embodiments of the present invention with specific embodiments thereof in conjunction with the accompanying drawings. The invention is capable of other and different embodiments and its several details are capable of modification in various other respects, all without departing from the spirit and scope of the present invention.
FIG. 2 is a system architecture diagram of a high availability rule stack implementation system of the present invention. As shown in fig. 2, the present invention provides a high availability rule stack implementation system, which includes:
the initial configuration unit 201 is configured to configure each worker as a worker node, divide all worker nodes into a plurality of node groups, each node group includes two nodes, and configure the nodes therein as a master node and a slave node.
A high availability rule configuration unit 202, configured to configure a high availability rule for each node group, where each rule configures one virtual IP, each rule virtual IP is always added to a corresponding master node, and a heartbeat line is added, all the master nodes with high availability rules carry high availability services of the high availability rule, and synchronize some data information with the corresponding slave nodes through associated replication rules.
In an embodiment of the present invention, as shown in FIG. 3, it is assumed that there is a working machine A, B, A1、B1、C、D、C1、D1、E、F、E1、F1、G、H、G1、H1Will work machine A, B, A1、B1、C、D、C1、D1、E、F、E1、F1、G、H、G1、H1Configured as node A, B, A1、B1、C、D、C1、D1、E、F、E1、F1、G、H、G1、H1And divide it into node groups AB, A1B1、CD、C1D1、EF、E1F1、GH、G1H1Adding high availability rules AB and A for each node group1B1、CD、C1D1、EF、E1F1、GH、G1H1Each rule is provided with a virtual IP, and the heartbeat lines of the master node and the slave nodes are added, the master nodes of all the rules bear the high available service of the rule, and some high available data information is synchronized to the corresponding slave nodes through the associated replication rule.
The stacking unit 203 is configured to regard each node group of the lower level as a whole as a node layer by layer, divide a plurality of father node groups, configure each whole node of each father node group as a master node and a slave node, configure a high availability rule for each father node group by using the high availability rule configuration unit 202, configure a virtual IP for each rule, and set a heartbeat line until only the last father node group remains, so as to realize high availability rule stacking, the High Availability (HA) rule at the bottom layer carries HA stacking rule high availability service information, and the rule heartbeat line of each father node group uses the virtual IP and the network card of the high availability rule of each node as connection.
Specifically, with continued reference to FIG. 3, node groups AB and A are identified1B1、CD、C1D1、EF、E1F1、GH、G1H1Respectively regarded as a whole as a node A2、B2、C2、D2、E2、F2、G2、H2Subdivided into parent node group A2B2、C2D2、E2F2、G2H2And adding a stacking high availability rule A2B2、C2D2、E2F2、G2H2Each rule is configured with a virtual IP, A2B2A rule treats AB as the whole as the master node A of the rule2A is1B1Slave node B as a whole for this rule2. Then the master node a in the AB high availability rule not only needs to carry rule AB but also carries rule a2B2The data information is all present on the master node a, a2B2Rules AB, A for rule-centric jumpers1B1The virtual IP and the network card as connection, A2B2Master node A to A with regular data transmission AB1B1Of the master node A1。C2D2、E2F2、G2H2And A2B2The rules are similar and will not be described herein.
Then, each father node is grouped into A2B2、C2D2、E2F2、G2H2Regarding each node group as a whole as a node A as a child node group3、C3、E3、G3And is again divided into a parent node group A3C3、E3G3Add Stack high availability rule A3C3、E3G3Configuring regular virtual IP, A3C3Rule A2B2Main node A as a whole as this rule3Mixing C with2D2Slave node C as a whole as the rule3Then A is2B2High availability rule middle master node A2Need to bear a3C3Further, the master node A of its child node group needs to carry AB, A2B2、A3C3All highly available services, the highly available configuration information for the three rules, are present on the primary node a. A. the3C3The core jumper wire is rule A2B2、C2D2As a connection, A3C3Is A2B2Of the master node A2To C2D2Master node C of2。E3G3Rule and A3C3Similarly.
And so on, each father node group A3C3、E3G3As a child node group, each node group is taken as a whole as a node A4、E4Adding rule A4E4Configure the regular virtual IP, A4E4Rule A3C3Main node A as a whole as this rule4E is3G3Slave node E as a whole for the rule4Rule A3C3Need to bear a4E4So that the master node a of rule AB needs to carry the rules AB, a2B2、A3C3、A4E4The highly available configuration information of the four rules all exist on the primary node a, a4E4The heart beat line of A3C3And E3G3Virtual IP and network card connection of, A4E4Is A3C3Of the master node A3To E3G3Master node E of3。
FIG. 4 is a flowchart illustrating steps of a method for implementing rule stacking according to the present invention. As shown in fig. 4, the method for implementing high-availability rule stacking of the present invention includes the following steps:
step S1, configuring each working machine as a working node, dividing all working nodes into a plurality of node groups, each node group comprises two nodes, configuring the nodes as a master node and a slave node, configuring a high availability rule for each node group, namely a high availability rule, and configuring the high availability rule by a master node and a slave node in the node group, configuring a virtual IP for each high availability rule, always adding each rule virtual IP on the corresponding master node, adding a heartbeat wire for the master node and the slave node, bearing the high availability service of the high availability rule by all the regular master nodes, and synchronizing some high availability data information to the corresponding slave node through an associated replication rule. In the invention, each node can provide complete data storage, access and command execution management service, the nodes are connected through a private network, the invention can provide a configuration interface, a master node and a slave node are determined for the nodes in each node group in a manual configuration mode, the high availability rule is used for ensuring the data synchronization consistency among all the nodes in the command processing process, and in the application, the high availability rule is a protocol for carrying out command processing among the nodes.
In an embodiment of the present invention, as shown in FIG. 3, it is assumed that there is a working machine A, B, A1、B1、C、D、C1、D1、E、F、E1、F1、G、H、G1、H1Will work machine A, B, A1、B1、C、D、C1、D1、E、F、E1、F1、G、H、G1、H1Configured as node A, B, A1、B1、C、D、C1、D1、E、F、E1、F1、G、H、G1、H1And divide it into node groups AB, A1B1、CD、C1D1、EF、E1F1、GH、G1H1Adding high availability rules AB and A for each node group1B1、CD、C1D1、EF、E1F1、GH、G1H1Each rule is provided with a virtual IP, and the heartbeat lines of the master node and the slave nodes are added, the master nodes of all the rules bear the high available service of the rule, and some high available data information is synchronized to the corresponding slave nodes through the associated replication rule.
Step S2, regarding each node group as a whole as a node, dividing the node group into a plurality of father node groups again, where each original node group is called a child node group of the corresponding father node group, and similarly, configuring each whole node of each father node group as a master node and a slave node, and configuring a high availability rule for each father node group, that is, configuring between the master node and the slave node in the father node group, each rule configuring a virtual IP, and setting a heartbeat line, where the regular heartbeat lines of each father node group are connected by using the virtual IP of each node rule and a network card as network cards, and the master node in the high availability rule of the child node group as the master node in the father node group needs to bear not only the high availability rule of the child node group but also the high availability service of the high availability rule of the corresponding father node group, and data information is stored on the master node of the child node group.
Specifically, node groups AB and A1B1、CD、C1D1、EF、E1F1、GH、G1H1Respectively regarded as a whole as a node A2、B2、C2、D2、E2、F2、G2、H2Subdivided into parent node group A2B2、C2D2、E2F2、G2H2And adding a stacking high availability rule A2B2、C2D2、E2F2、G2H2Each rule is configured with a virtual IP, A2B2Rule treats AB as an integerThe entity is the master node A of the rule2A is1B1Slave node B as a whole for this rule2. Then the master node a in the AB high availability rule not only needs to carry rule AB but also carries rule a2B2The data information is all present on the master node a, a2B2Rules AB, A for rule-centric jumpers1B1The virtual IP and the network card as connection, A2B2Master node A to A with regular data transmission AB1B1Of the master node A1。C2D2、E2F2、G2H2And A2B2The rules are similar and will not be described herein.
And step S3, taking each father node group as a child node group, returning to the step S2, and stacking the high availability rules again until only the last father node group is left.
Specifically, each parent node is grouped into a2B2、C2D2、E2F2、G2H2Regarding each node group as a whole as a node A as a child node group3、C3、E3、G3And is again divided into a parent node group A3C3、E3G3Add Stack high availability rule A3C3、E3G3Configuring regular virtual IP, A3C3Rule A2B2Main node A as a whole as this rule3Mixing C with2D2Slave node C as a whole as the rule3Then A is2B2High availability rule middle master node A2Need to bear a3C3Further, the master node A of its child node group needs to carry AB, A2B2、A3C3All highly available services, the highly available configuration information for the three rules, are present on the primary node a. A. the3C3The core jumper wire is rule A2B2、C2D2As a connection, A3C3Is A2B2Of the master node A2To C2D2Master node C of2。E3G3Rule and A3C3Similarly.
And so on, each father node group A3C3、E3G3As a child node group, each node group is taken as a whole as a node A4、E4Adding rule A4E4Configure the regular virtual IP, A4E4Rule A3C3Main node A as a whole as this rule4E is3G3Slave node E as a whole for the rule4Rule A3C3Need to bear a4E4So that the master node a of rule AB needs to carry the rules AB, a2B2、A3C3、A4E4The high available configuration information for these four rules all exist on primary node a. A. the4E4The heart beat line of A3C3And E3G3The virtual IP and the network card are connected. A. the4E4Is A3C3Of the master node A3To E3G3Master node E of3。
So far, the parent node group only remains the parent node group A4、、E4And the stacking process is ended.
Fig. 5 is a schematic diagram of the operation of high availability rule stacking according to the present invention, mainly completing the establishment and data synchronization of functional heartbeat lines, and the underlying High Availability (HA) rule carries HA stacking rule high availability service information. The process is as follows:
1. establishing high availability rules AB and A1B1、CD、C1D1And A2B2、C2D2Then, a regular virtual IP is configured, and the regular virtual IP is always added to the main node.
2. If the main node A is down, the heartbeat lines 1 and 3 are disconnected, the associated replication rule stops data synchronization, the main node A stops providing service, and the slave node B is switched to be the main node.
3. For rule A2B2Only when the sub-rule AB is completely down, it is equivalent to A2When the machine is down, the heart beat wire 3 is completely disconnected, A2B2Regular slave node B2It will switch to the master node. Therefore, after the slave node B is switched to the master node, the high availability rule AB carried by the old master node A and the father rule A thereof2B2And A3C3The high available service information is switched to a new main node B, the virtual IP of the AB rule is also added to the new main node B, and the heartbeat line 3 is switched to the node A again1And B, establishing connection. Then stacking rule A2B2、C2D2、A3C3Still normally operating, when B bears all the stacking rules A2B2、C2D2、A3C3High available service.
4. If node B is down, AB is down, that is, main node A2Downtime, disconnection of the heart wires 3, 7, and rule A stacking2B2From node B2Switching to the master node.
5. For rule A3C3Only when A2、B2In case of all downtime, it is equivalent to A3When the machine is down, the heart beat wire 7 is completely disconnected, A3C3Slave node C of a rule3It will switch to the master node. Thus when B is2After the main node is switched, the regular virtual IP is added again, and the heartbeat line 7 is at C2、B2Reestablishes the connection therebetween. At this time B2I.e. node A1Bearer Stack rule A3C3High available service information.
6. For B2To say, only A1、B1All downtime is equivalent to B2And (6) shutting down. If A is in this case1、B1All crashes, i.e. B2Downtime, i.e. A3When the system is down, the heartbeat line 7 is disconnected, and the slave node C3Switching to the master node. At this time C3Sub-rule C of2D2Is a master node of C2，C2The sub-rule of (1) is CD and the master node is C. Node A1Upper bearer stacking rule A3C3The high-availability service information is switched to the main node C, and the C node carries the C2D2And high available service information of the CD.
And (3) according to the whole stacking rule, establishing a heartbeat wire according to the virtual IP of the rule, and performing data transmission by the regular main node.
As can be seen, in this embodiment, when the master node a goes down, the master node of rule AB is switched from node a to node B, and the high-availability rule a is stacked2B2、A3C3、A4C4The high-availability service can still run normally, thereby ensuring the continuity of the service and increasing the sustainable protection capability of the data.
In summary, the high availability rule stacking system and method of the present invention implement high availability rule stacking by configuring each working machine as a working node, dividing all working nodes into a plurality of node groups, configuring the nodes of each node group as a master node and a slave node, configuring a high availability rule for each node group, configuring a virtual IP for each rule, adding a heartbeat line, regarding each node group of the next level as a whole as a node layer by layer, dividing a plurality of parent node groups, configuring each node of each parent node group as a master node and a slave node, configuring a high availability rule for each parent node group by using the high availability rule configuration unit, configuring a virtual IP for each rule, and setting a heartbeat line until the last parent node group, so that a large batch of machines can still provide service continuously when a crash occurs, the downtime is shortened. The invention is the upgrading of the common HA function, which is similar to the stacking of a plurality of HAs, and finally forms the high available service of an outermost HA master-slave node to protect data.
The foregoing embodiments are merely illustrative of the principles and utilities of the present invention and are not intended to limit the invention. Modifications and variations can be made to the above-described embodiments by those skilled in the art without departing from the spirit and scope of the present invention. Therefore, the scope of the invention should be determined from the following claims.
Claims (8)
1. A high availability rule stack implementation system, comprising:
the initial node configuration unit is used for configuring each working machine as a working node, dividing all the working nodes into a plurality of node groups, wherein each node group comprises two nodes, and configuring the nodes of each node group as a master node and a slave node;
the high-availability rule configuration unit is used for configuring high-availability rules for each node group, configuring a virtual IP for each rule and adding a heartbeat line;
and the stacking unit is used for regarding each node group of the lower level as a whole as a node layer by layer, dividing a plurality of father node groups, configuring the nodes of each father node group into a main node and a slave node, configuring a high availability rule for each father node group by using the high availability rule configuration unit, configuring a virtual IP for each rule, and setting a heartbeat line until the last father node group so as to realize high availability rule stacking.
2. The high availability rules stack implementation system of claim 1, wherein: the regular heart line of each father node group uses the virtual IP and the network card of each node as connection.
3. The high availability rules stack implementation system of claim 1, wherein: the virtual IP of each rule is added on the corresponding master node.
4. The high availability rules stack implementation system of claim 1, wherein: each high-availability rule of the bottom layer carries high-availability service information of the rule stacked by the corresponding stacking unit.
5. A high availability rule stacking implementation method comprises the following steps:
step S1, configuring each working machine as a working node, dividing all the working nodes into a plurality of node groups, wherein each node group comprises two nodes, configuring the nodes of each node group as a main node and a slave node, configuring high-availability rules for each node group, configuring a virtual IP for each rule, and adding a heartbeat line;
step S2, regarding each node group as a whole as a node, dividing the node group into a plurality of father node groups again, wherein each original node group is called as a child node group of the corresponding father node group, configuring the nodes of each father node group as a main node and a slave node, configuring high-availability rules for each father node group, configuring a virtual IP for each rule, and setting a heartbeat line;
and step S3, taking each father node group as a child node group, returning to step S2, and stacking the high availability rules again until the last father node group.
6. The method of claim 5, wherein the rule stack implementation method comprises: in step S1, all the master nodes of the rule carry the highly available service of the highly available rule, and synchronize some data information of the highly available rule to the corresponding slave nodes through the associated replication rule.
7. The method of claim 6, wherein the rule stack implementation method comprises: each rule virtual IP is added on a corresponding master node.
8. The method of claim 7, wherein the rule stack implementation method comprises: in step S2, the rule-based core jumper of each parent node group uses the virtual IP and the network card of each node rule as a connection.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911175790.6A CN110855505B (en) | 2019-11-26 | 2019-11-26 | High-availability rule stacking implementation system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911175790.6A CN110855505B (en) | 2019-11-26 | 2019-11-26 | High-availability rule stacking implementation system and method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110855505A true CN110855505A (en) | 2020-02-28 |
| CN110855505B CN110855505B (en) | 2022-03-04 |
Family
ID=69604722
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911175790.6A Active CN110855505B (en) | 2019-11-26 | 2019-11-26 | High-availability rule stacking implementation system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110855505B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102724069A (en) * | 2012-06-14 | 2012-10-10 | 福建星网锐捷网络有限公司 | Collision detection method, device and network device of dual-master device in thermal staking system |
| US8412672B1 (en) * | 2010-09-08 | 2013-04-02 | Netapp, Inc. | High availability network storage system incorporating non-shared storage suitable for use with virtual storage servers |
| US20140169168A1 (en) * | 2012-12-06 | 2014-06-19 | A10 Networks, Inc. | Configuration of a virtual service network |
| CN106713468A (en) * | 2016-12-29 | 2017-05-24 | 深圳云天励飞技术有限公司 | Distributed cluster service structure and node cooperation method thereof |
-
2019
- 2019-11-26 CN CN201911175790.6A patent/CN110855505B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8412672B1 (en) * | 2010-09-08 | 2013-04-02 | Netapp, Inc. | High availability network storage system incorporating non-shared storage suitable for use with virtual storage servers |
| CN102724069A (en) * | 2012-06-14 | 2012-10-10 | 福建星网锐捷网络有限公司 | Collision detection method, device and network device of dual-master device in thermal staking system |
| US20140169168A1 (en) * | 2012-12-06 | 2014-06-19 | A10 Networks, Inc. | Configuration of a virtual service network |
| CN106713468A (en) * | 2016-12-29 | 2017-05-24 | 深圳云天励飞技术有限公司 | Distributed cluster service structure and node cooperation method thereof |
Non-Patent Citations (3)
| Title |
|---|
| HUA GUO,LINGJIAO WANG: "LMA/HA Discovery Mechanism on the interaction between MIPv6 and PMiPv6", 《2009 5TH INTERNATIONAL CONFERENCE ON WIRELESS COMMUNICATIONS,NETWORKING AND MOBILE COMPUTING》 * |
| WEIXIN_34149796: "FortiGate防火墙HA下联堆叠交换机", 《CSDN》 * |
| 陈光礼: "基于堆叠系统业务不中断升级的设计与实现", 《中国优秀硕士学位论文数据库》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110855505B (en) | 2022-03-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP5352115B2 (en) | Storage system and method for changing monitoring condition thereof | |
| CN103176831B (en) | A kind of dummy machine system and management method thereof | |
| CN102394914A (en) | Cluster brain-split processing method and device | |
| CN111935244B (en) | Service request processing system and super-integration all-in-one machine | |
| CN108984320A (en) | A kind of anti-fissure method and device of message queue cluster | |
| CN113438111A (en) | Method for restoring RabbitMQ network partition based on Raft distribution and application | |
| WO2017097006A1 (en) | Real-time data fault-tolerance processing method and system | |
| CN112527567A (en) | System disaster tolerance method, device, equipment and storage medium | |
| CN113515408A (en) | Data disaster tolerance method, device, equipment and medium | |
| CN109361777A (en) | Synchronous method, synchronization system and the relevant apparatus of distributed type assemblies node state | |
| CN112783694B (en) | Long-distance disaster recovery method for high-availability Redis | |
| CN102487332B (en) | Fault processing method, apparatus thereof and system thereof | |
| JP5358310B2 (en) | Input / output management method and input / output unit integrated dual station apparatus in input / output unit integrated dual station apparatus | |
| WO1997049034A1 (en) | Job taking-over system | |
| CN110855505B (en) | High-availability rule stacking implementation system and method | |
| CN107181608B (en) | Method for recovering service and improving performance and operation and maintenance management system | |
| CN114124803B (en) | Device management method and device, electronic device and storage medium | |
| JP2015114952A (en) | Network system, monitoring control unit, and software verification method | |
| CN104503871A (en) | Implementation method based on full-redundancy model of small computer system | |
| CN107483257A (en) | A kind of application system dispositions method and framework based on X86 and ARM hybird environments | |
| JPH04311251A (en) | Multiprocessor system | |
| WO2019216210A1 (en) | Service continuation system and service continuation method | |
| CN101453354A (en) | High availability system based on ATCA architecture | |
| JP6555353B2 (en) | Cluster system, information processing apparatus, cluster system synchronization method, and program | |
| JP2011159222A (en) | Server system and control method thereof |
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 |