Custom detection group detection result synchronization method and device

Abstract

The invention discloses a method and a device for synchronizing detection results of a user-defined detection group. The method comprises the following steps: receiving a detection result synchronization message sent by other equipment nodes in a cluster; the detection result synchronization message comprises a service resource id and a detection result; according to the service resource id and the local node service configuration, obtaining a user-defined detection group id for executing detection for the service resource; performing validity verification on the synchronous source node according to the user-defined detection group id to obtain a verification result; and aggregating the detection results of different Leader nodes in the self-defined detection group according to the verification result. According to the method and the device for synchronizing the detection results of the user-defined detection group, illegal synchronization can be avoided through legality verification of the synchronization source node, and the problem of alternate coverage of the synchronization results of equipment nodes in a cluster in the prior art is solved by aggregating the detection results of different Leader nodes; and the accuracy of the synchronization result in the user-defined detection group is ensured.

Description

Technical Field

[0001] The present application relates to the technical field of detection result synchronization, and in particular to a method and device for synchronizing detection results of a custom detection group. Background Art

[0002] With the rapid development of Internet technology, users have higher requirements for service availability, response speed and data security, and the service model of a single data center is difficult to meet these requirements. Therefore, multi-data center deployment has become a trend. Multi-data center is to build multiple data centers in different geographical locations, which can significantly improve service availability, response speed and user experience, while enhancing business continuity and security.

[0003] In a multi-data center architecture, global server load balancing (GSLB) technology is particularly important. It uses technologies such as DNS resolution, health checks, and intelligent routing to achieve intelligent scheduling and traffic optimization of user requests, routing requests to the nearest or most appropriate service resources, thereby achieving the goal of optimizing response speed and service quality.

[0004] One of the core functions of GSLB is health check, which can perform real-time health monitoring of service resources located in different geographical locations and data centers, monitor and evaluate the availability and performance of service resources, and quickly identify risks such as node failure or performance degradation. Through intelligent load balancing algorithms, GSLB can automatically redirect traffic to healthy resource nodes, thereby avoiding service interruptions caused by single point failures and improving the overall availability and fault tolerance of the system.

[0005] In a multi-data center scenario, each data center usually has multiple carrier network lines. To ensure accurate detection availability even when a data center or a carrier line fails or performance degrades, a custom detection group function is usually configured. Figure 1 For example, custom detection group 1 selects detection nodes on different exit lines in three data centers in two locations to form a detection node pool. Point-to-point connections are established between the nodes. The three nodes negotiate through a weighted election algorithm to select Unicom detection node 1 as the leader node. In each detection cycle, the leader node selects a node from the detection pool based on the algorithm to perform detection on service resources.

[0006] Due to program anomalies, export network or transmission link reasons, different detection nodes may have different detection results for the same target service resource. In order to more accurately determine whether the target service resource is available, the Leader node will determine whether the detection results of all detection nodes within the failure delay response time are continuously failed: if so, the current state of the target service resource is considered unavailable; otherwise, as long as the detection result of any detection node in the custom detection group is successful, the service resource is considered available. The Leader node will synchronize the detection result to all nodes in the cluster to ensure the consistency of the detection results on all GSLB devices.

[0007] If a detection node in a custom detection group is disconnected from the network management node or the leader node in the custom detection group due to a network firewall or transmission link problem, the following error message will appear: Figure 2 The problems shown are as follows:

[0008] 1. Modify the configuration to remove Telecom Detection Node 2 from Custom Detection Group 1. Since Telecom Detection Node 2 is disconnected from the network management node, it cannot receive the latest configuration. Other nodes in the cluster can receive the Custom Detection Group configuration modification message normally and update the local Custom Detection Group 1 configuration respectively.

[0009] 2. Telecom detection node 2 and Unicom detection node 1 are disconnected. Based on the weighted election algorithm, the node will select this node as the new leader node;

[0010] 3. There are two leader nodes in the custom detection group 1. Since the network connection is disconnected, there is no interaction between the two leader nodes. China Unicom detection node 1 selects China Unicom detection node 1 and China Mobile detection node 1 to perform detection in turn, and China Telecom detection node 2 selects this node to perform detection;

[0011] 4. If the detection result of the service resource by the Unicom detection node 1 or the mobile detection node 1 is normal, the Unicom detection node 1 determines that the state of the target service resource is available;

[0012] 5. If the detection result of the telecommunication detection node 2 on the service resource is a failure, the telecommunication detection node 2 determines that the service resource is unavailable;

[0013] 6. The two leader nodes, Unicom Detection Node 1 and Telecom Detection Node 2, will synchronize their respective detection results to other device nodes in the cluster. Assume that Mobile Detection Node 2 first receives the service resource detection result synchronized by Unicom Detection Node 1 as available, and then receives the service resource detection result synchronized by Telecom Detection Node 2 as unavailable. The final effective detection result is unavailable, resulting in the inability to resolve the service resource normally.

[0014] In summary, the prior art has the following defects:

[0015] 1. After multiple Leader nodes appear, the detection results will be alternately covered: After multiple Leader nodes appear in the same custom detection group, each Leader node determines the detection result, and some Leader nodes will have detection results of down and some will have detection results of up. After other device nodes in the cluster receive the service resource detection result synchronization message sent by the Leader node, they will take the latest synchronization result received as the standard, which will eventually lead to the problem of alternating coverage of erroneous detection results and normal detection results. For details, see Figure 3 .

[0016] 2. Failure to determine whether the synchronization source node belongs to the custom detection group: After some nodes in the custom detection group are disconnected from the network management node, they cannot receive the synchronization group configuration modification message. The node may have been deleted from the synchronization group, but it will still send detection result synchronization messages to other device nodes in the cluster, causing the detection results maintained by these nodes to be inconsistent with the actual situation. Summary of the invention

[0017] To this end, the present application provides a method and device for synchronizing detection results of a custom detection group to solve the problem that the detection results will be alternately overwritten and the detection results will be inaccurate after multiple Leader nodes appear in the prior art.

[0018] In order to achieve the above objectives, this application provides the following technical solutions:

[0019] In a first aspect, a method for synchronizing detection results of a custom detection group is provided, the method being applied to a device node in a cluster, comprising:

[0020] Receive a detection result synchronization message sent by other device nodes in the cluster; the detection result synchronization message includes a service resource id and a detection result;

[0021] According to the service resource ID and the local node business configuration, obtain a custom detection group ID for performing detection for the service resource;

[0022] Perform validity verification on the synchronization source node according to the custom detection group ID to obtain a verification result;

[0023] The detection results of different Leader nodes in the custom detection group are aggregated according to the verification result.

[0024] Optionally, the validity of the synchronization source node is verified according to the custom detection group ID to obtain a verification result, which is specifically:

[0025] Determine whether the synchronization source node is a member node in the custom detection group id;

[0026] If the synchronization source node is not a member node in the custom detection group id, the detection result is discarded;

[0027] If the synchronization source node is a member node in the custom detection group id, the detection results of different leader nodes in the custom detection group are aggregated.

[0028] Optionally, aggregating the detection results of different leader nodes in the custom detection group specifically includes:

[0029] Determine whether the detection result is up;

[0030] If the detection result is up, the locally saved service resource detection result is updated to available, and it is determined whether the service resource starts the detection failure timer. If it is started, the detection failure timer is turned off;

[0031] If the detection result is down, determine whether the service resource has started the detection failure timer. If so, the processing ends. If not, start the detection failure timer for the service resource. If the detection failure timer times out, set the detection result of the service resource to unavailable.

[0032] Optionally, the timeout duration of the detection failure timer is the detection template failure delayed response time.

[0033] In a second aspect, a custom detection group detection result synchronization device includes:

[0034] A data receiving module, used to receive a detection result synchronization message sent by other device nodes in the cluster; the detection result synchronization message includes a service resource ID and a detection result;

[0035] A custom detection group ID determination module, used to obtain a custom detection group ID for performing detection for the service resource according to the service resource ID and the local node business configuration;

[0036] A verification module, used to verify the validity of the synchronization source node according to the custom detection group ID to obtain a verification result;

[0037] The aggregation module is used to aggregate the detection results of different Leader nodes in the custom detection group according to the verification result.

[0038] Optionally, the verification module is specifically used to:

[0039] Determine whether the synchronization source node is a member node in the custom detection group id;

[0040] If the synchronization source node is not a member node in the custom detection group id, the detection result is discarded;

[0041] If the synchronization source node is a member node in the custom detection group id, the detection results of different leader nodes in the custom detection group are aggregated.

[0042] Optionally, the aggregation module is specifically used for:

[0043] Determine whether the detection result is up;

[0044] If the detection result is up, the locally saved service resource detection result is updated to available, and it is determined whether the service resource starts the detection failure timer. If it is started, the detection failure timer is turned off;

[0045] If the detection result is down, determine whether the service resource has started the detection failure timer. If so, the processing ends. If not, start the detection failure timer for the service resource. If the detection failure timer times out, set the detection result of the service resource to unavailable.

[0046] Optionally, the timeout duration of the detection failure timer is the detection template failure delayed response time.

[0047] In a third aspect, a computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of a method for synchronizing detection results of a custom detection group.

[0048] In a fourth aspect, a computer program product includes a computer program or instructions, which, when executed by a processor, perform steps of a method for synchronizing detection results of a custom detection group.

[0049] Compared with the prior art, this application has at least the following beneficial effects:

[0050] The present application provides a method and device for synchronizing detection results of a custom detection group, which receives detection result synchronization messages sent by other device nodes in the cluster; the detection result synchronization messages contain service resource IDs and detection results; according to the service resource ID and the local node business configuration, a custom detection group ID for performing detection for the service resource is obtained; according to the custom detection group ID, the validity of the synchronization source node is verified to obtain the verification result; according to the verification result, the detection results of different Leader nodes in the custom detection group are aggregated. The method and device for synchronizing detection results of a custom detection group provided by the present application can avoid illegal synchronization by verifying the legitimacy of the synchronization source node, and solves the problem of alternating coverage of synchronization results of device nodes in the cluster in the prior art by aggregating the detection results of different Leader nodes, thereby ensuring the accuracy of the synchronization results in the custom detection group. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] In order to more intuitively illustrate the prior art and the present application, exemplary drawings are given below. It should be understood that the specific shapes and structures shown in the drawings should not generally be regarded as limiting conditions for implementing the present application; for example, those skilled in the art are capable of easily making conventional adjustments or further optimizations to the addition / reduction / attribution division, specific shapes, positional relationships, connection methods, dimensional ratios, etc. of certain units (components) based on the technical concepts and exemplary drawings disclosed in the present application.

[0052] Figure 1 This is a schematic diagram of the custom detection group structure;

[0053] Figure 2 This is a schematic diagram of the structure of multiple Leader nodes in a custom detection group;

[0054] Figure 3 Synchronize the processing flow chart for the existing detection results;

[0055] Figure 4 A flow chart of a method for synchronizing detection results of a custom detection group provided in this application;

[0056] Figure 5 A judgment flow chart of a custom detection group detection result synchronization method provided in this application. DETAILED DESCRIPTION

[0057] The present application is further described below in detail through specific embodiments in conjunction with the accompanying drawings.

[0058] In the description of this application: unless otherwise specified, the meaning of "plurality" is two or more. The terms "first", "second", "third", etc. in this application are intended to distinguish the objects referred to, and do not have special meanings in terms of technical connotations (for example, they should not be understood as emphasizing the importance or order, etc.). Expressions such as "including", "comprising", "having", etc. also mean "not limited to" (certain units, components, materials, steps, etc.).

[0059] The terms such as "upper", "lower", "left", "right", "middle", etc. cited in this application are usually used to indicate the general relative position relationship for the purpose of intuitive understanding by referring to the drawings, and are not absolute limitations on the position relationship in the actual product.

[0060] See also Figure 4 The present application provides a method for synchronizing detection results of a custom detection group, which is applied to a device node (i.e., a Leader node) in a cluster, including:

[0061] S1: Receive the detection result synchronization message sent by other device nodes in the cluster; the detection result synchronization message contains the service resource ID and the detection result;

[0062] S2: According to the service resource ID and the local node business configuration, obtain the custom detection group ID for performing detection for the service resource;

[0063] Specifically, after receiving the detection result synchronization message, the device node obtains the custom detection group ID for performing detection for the service resource according to the service resource ID and the business configuration saved by the node.

[0064] S3: Verify the validity of the synchronization source node according to the custom detection group ID and obtain the verification result;

[0065] See also Figure 5 In this step, the validity check of the synchronization source node is performed according to the custom detection group ID:

[0066] S301: Determine whether the synchronization source node is a member node in the custom detection group ID;

[0067] S302: If the synchronization source node is not a member node in the custom detection group ID, the detection result is discarded;

[0068] Specifically, if the synchronization source node is not a member node in the custom detection group ID, it means that the synchronization source is incorrect, which is an abnormal scenario, so the detection result will be discarded.

[0069] S303: If the synchronization source node is a member node in the custom detection group ID, the detection results of different leader nodes in the custom detection group are aggregated.

[0070] In this step, when checking the validity of the synchronization node, the device node will check the validity of the synchronization source node only after receiving the synchronization message. During the validity check, it is determined whether the synchronization source node belongs to the custom detection group that performs detection on the service resource. Only when it does, the synchronization node is considered legal.

[0071] S4: Aggregate the detection results of different Leader nodes in the custom detection group according to the verification results.

[0072] Continue reading Figure 5 In this step, the detection results of different leader nodes in the custom detection group are aggregated, including:

[0073] S401: Determine whether the detection result is up;

[0074] S402: If the detection result is up, the locally stored service resource detection result is updated to be available, and it is determined whether the service resource starts the detection failure timer. If it is started, the detection failure timer is turned off;

[0075] Specifically, if the synchronization source node is a member node in the custom detection group id, it is determined whether the synchronized detection result is up. If the detection result is up, the locally saved detection result of the service resource is updated to be available; then it is determined whether the detection failure timer of the service resource has been started. If it has been started, the detection failure timer is turned off and the process ends.

[0076] S403: If the detection result is down, determine whether the service resource has started the detection failure timer. If so, the process ends. If not, start the detection failure timer for the service resource. If the detection failure timer times out, set the detection result of the service resource to unavailable.

[0077] Specifically, if the result of the synchronized detection is down, the locally saved detection result of the service resource will not be updated; instead, it is determined whether the detection failure timer of the service resource has been started. If it has been started, it means that other leader nodes in the custom detection group have sent synchronization messages with detection results of down, and no further processing is required, and the process ends; if the detection failure timer has not been started, a detection failure timer is started for the service resource, and the detection failure timer timeout duration is the detection template failure delay response time. If the detection failure timer times out, it means that there is no leader node in the custom detection group with a detection result of up, and the detection result of the service resource is set to unavailable.

[0078] In other words, when the synchronization results of different leader nodes in a custom detection group are aggregated, the detection result synchronization messages sent by different leader nodes in the same custom detection group are aggregated. As long as the detection result of any leader node is up, the detection result of the custom detection group for the service resource is considered to be available.

[0079] In a method for synchronizing detection results of a custom detection group provided by the present application, when a device node in a cluster receives a detection result synchronization message, it is necessary to aggregate the detection results of different Leader nodes in the custom detection group. Specifically: comprehensively judge the detection results of these Leader nodes, and only when the detection results of the Leader nodes in the same custom detection group are all down, update the locally saved detection result of the service resource to unavailable; otherwise, as long as there is one detection result that is up, immediately set the detection result to available. When multiple Leader nodes are formed in a custom detection group due to network disconnection between nodes, when different Leader nodes have different detection results for the same service resource, the detection results finally synchronized by all nodes in the cluster are still accurate.

[0080] The method for synchronizing detection results of a custom detection group provided in this application has the following advantages:

[0081] 1. The validity verification of the synchronization source node can avoid illegal synchronization: The device nodes in the cluster perform validity verification on the synchronization source node, which solves the problem that after the Leader node is disconnected from the network management node, it cannot receive the configuration modification to delete it from the custom detection group, thereby causing the synchronization of illegal detection results.

[0082] 2. The synchronization result aggregation process ensures the accuracy of the synchronization results within the custom detection group: When multiple Leader nodes are formed due to device disconnection within the custom detection group, even if different Leader nodes have different detection results for the same service resource, by aggregating the synchronization results of different Leader nodes, the accuracy and effectiveness of the synchronization results within the custom detection group can be guaranteed, solving the problem of alternating coverage of synchronization results of device nodes within the cluster in the prior art.

[0083] Embodiment 1

[0084] The detection node is disconnected from the Leader node in the custom detection:

[0085] Continue reading Figure 2 , when the telecom detection node 2 is disconnected from the leader node, there are two leader nodes in the custom detection group 1. The detection result of the telecom detection node 2 for the service resource is down, and the detection result of the Unicom detection node 1 or the mobile detection node 1 is up. Both leader nodes will broadcast and synchronize the detection results in the cluster.

[0086] The traditional processing method is: Mobile detection node 2 first receives the synchronization result of Unicom detection node 1 (the result is up), and then receives the synchronization result of Telecom detection node 2 (the result is down) 1 second later. The locally maintained detection result is updated from available to unavailable. In the next detection cycle, the coverage from available to unavailable will be repeated, which is inconsistent with the current actual availability of the service resource.

[0087] When the method provided by the present application is used for processing: the mobile detection node 2 first receives the synchronization result of the Unicom detection node 1 (the result is up), and updates the detection result maintained by this node to available. After 1 second, the synchronization result of the Telecom detection node 2 is received (the result is down). Since the synchronization result is down, the result maintained by this node is not updated for the time being, and the detection failure timer is started. In the next detection cycle, the synchronization result of the Unicom detection node 1 is up, and the detection failure timer is turned off. The detection result saved by the mobile detection node 2 is always available, which is consistent with the actual availability of the service resource.

[0088] Embodiment 2

[0089] The detection node is disconnected from the network management node and the leader node in the custom detection group:

[0090] Continue reading Figure 2 , when the telecom detection node 2 is disconnected from the network management node and the leader node respectively, there are two leader nodes in the custom detection group 1. Modify the configuration of the custom detection group 1 and delete the telecom detection node 2 from the custom detection group 1. The telecom detection node 2 cannot receive the latest configuration and still performs detection, and the detection result of down is broadcast and synchronized in the cluster.

[0091] The traditional processing method may cause illegal synchronization, because after the mobile detection node 2 receives the synchronization message from the telecommunication detection node 2 (the result is down), the detection result of the service resource will be updated to unavailable.

[0092] When the method provided in the present application is used for processing: after the mobile detection node 2 in the cluster receives the synchronization message, it obtains the custom detection group 1 that performs detection for the service resource based on the local configuration and the service resource ID. Since the telecommunications detection node 2 does not belong to the custom detection group 1, the synchronization message from the telecommunications detection node 2 will be discarded, and illegal synchronization will not occur.

[0093] The present application also provides a custom detection group detection result synchronization device, including:

[0094] A data receiving module, used to receive a detection result synchronization message sent by other device nodes in the cluster; the detection result synchronization message includes a service resource ID and a detection result;

[0095] A custom detection group ID determination module, used to obtain a custom detection group ID for performing detection for the service resource according to the service resource ID and the local node business configuration;

[0096] A verification module, used to verify the validity of the synchronization source node according to the custom detection group ID to obtain a verification result;

[0097] The aggregation module is used to aggregate the detection results of different Leader nodes in the custom detection group according to the verification result.

[0098] The verification module is specifically used for:

[0099] Determine whether the synchronization source node is a member node in the custom detection group id;

[0100] If the synchronization source node is not a member node in the custom detection group id, the detection result is discarded;

[0101] If the synchronization source node is a member node in the custom detection group id, the detection results of different leader nodes in the custom detection group are aggregated.

[0102] The aggregation module is specifically used for:

[0103] Determine whether the detection result is up;

[0104] If the detection result is up, the locally saved service resource detection result is updated to available, and it is determined whether the service resource starts the detection failure timer. If it is started, the detection failure timer is turned off;

[0105] If the detection result is down, it is determined whether the service resource starts the detection failure timer. If it is started, the processing ends; if it is not started, the detection failure timer is started for the service resource. If the detection failure timer times out, the detection result of the service resource is set to unavailable. Among them, the timeout length of the detection failure timer is the detection template failure delay response time.

[0106] For the specific implementation content of each module in a custom detection group detection result synchronization device, please refer to the above definition of a custom detection group detection result synchronization method, which will not be repeated here.

[0107] The present application also provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of a method for synchronizing detection results of a custom detection group are implemented.

[0108] The present application also provides a computer program product, including a computer program or instructions, which, when executed by a processor, perform steps of a method for synchronizing detection results of a custom detection group.

[0109] The technical features of the above embodiments may be arbitrarily combined (as long as there is no contradiction in the combination of these technical features). To make the description concise, not all possible combinations of the technical features in the above embodiments are described; these embodiments that are not explicitly written should also be considered to be within the scope of this specification.

Claims

1. A method for synchronizing detection results of a custom detection group, characterized in that: The method is applied to a device node in a cluster, and includes: Receive a detection result synchronization message sent by other device nodes in the cluster; the detection result synchronization message includes a service resource id and a detection result; According to the service resource ID and the local node business configuration, obtain a custom detection group ID for performing detection for the service resource; Perform validity verification on the synchronization source node according to the custom detection group ID to obtain a verification result; The detection results of different Leader nodes in the custom detection group are aggregated according to the verification result.

2. The method for synchronizing detection results of a custom detection group according to claim 1, characterized in that: The validity of the synchronization source node is verified according to the custom detection group ID to obtain the verification result, which is specifically: Determine whether the synchronization source node is a member node in the custom detection group id; If the synchronization source node is not a member node in the custom detection group id, the detection result is discarded; If the synchronization source node is a member node in the custom detection group id, the detection results of different leader nodes in the custom detection group are aggregated.

3. The method for synchronizing detection results of a custom detection group according to claim 2, characterized in that: The aggregating of the detection results of different leader nodes in the custom detection group specifically includes: Determine whether the detection result is up; If the detection result is up, the locally saved service resource detection result is updated to be available, and it is determined whether the service resource starts the detection failure timer. If it is started, the detection failure timer is turned off; If the detection result is down, determine whether the service resource has started the detection failure timer. If so, the processing ends. If not, start the detection failure timer for the service resource. If the detection failure timer times out, set the detection result of the service resource to unavailable.

4. The method for synchronizing detection results of a custom detection group according to claim 3, characterized in that: The timeout period of the detection failure timer is the detection template failure delayed response time.

5. A self-defined detection group detection result synchronization device, characterized in that: include: A data receiving module is used to receive detection result synchronization messages sent by other device nodes in the cluster; The detection result synchronization message includes the service resource id and the detection result; A custom detection group ID determination module, used to obtain a custom detection group ID for performing detection for the service resource according to the service resource ID and the local node business configuration; A verification module, used to verify the validity of the synchronization source node according to the custom detection group ID to obtain a verification result; The aggregation module is used to aggregate the detection results of different Leader nodes in the custom detection group according to the verification result.

6. The self-defined detection group detection result synchronization device according to claim 5, characterized in that: The verification module is specifically used for: Determine whether the synchronization source node is a member node in the custom detection group id; If the synchronization source node is not a member node in the custom detection group id, the detection result is discarded; If the synchronization source node is a member node in the custom detection group id, the detection results of different leader nodes in the custom detection group are aggregated.

7. The self-defined detection group detection result synchronization device according to claim 5, characterized in that: The aggregation module is specifically used for: Determine whether the detection result is up; If the detection result is up, the locally saved service resource detection result is updated to be available, and it is determined whether the service resource starts the detection failure timer. If it is started, the detection failure timer is turned off; If the detection result is down, determine whether the service resource starts the detection failure timer. If so, the process ends; If not started, a detection failure timer is started for the service resource. If the detection failure timer times out, the detection result of the service resource is set to unavailable.

8. The self-defined detection group detection result synchronization device according to claim 7, characterized in that: The timeout period of the detection failure timer is the detection template failure delayed response time.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 4 are implemented.

10. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 4 are implemented.

Images