Service unit switching method, system, and device for disaster tolerance switching and capacity dispatching
A method, a system, and a device for switching a service unit are provided. The method includes: determining a target service unit; and triggering the target service unit to publish first routing information according to configuration information of a first service unit for a first load balancing task, so as to replace the first service unit to provide a traffic distribution service for the first load balancing task. When the entire service network needs to perform disaster tolerance switching and capacity dispatching, the method provided in the embodiments of this application can effectively improve the real-time performance of traffic switching, and avoid the problem of relatively poor real-time performance of traffic switching caused by the influence of DNS cache in the existing technologies.
1. A method implemented by a computing device, the method comprising:
determining a target service unit; and
triggering the target service unit to publish first routing information according to configuration information of a first service unit for a first load balancing task, to replace the first service unit to provide a traffic distribution service for the first load balancing task, wherein:
attributes of a connection previously established by the first service unit for the first load balancing task have no change before and after the target service unit takes over the first service unit to provide the traffic distribution service for the first load balancing task;
the first routing information published by the target service unit includes network segment information about a virtual service address configured by the first service unit for the first load balancing task; and
a number after a designated symbol in the network segment information in the first routing information is larger than a number after the designated symbol in network segment information in second routing information published by the first service unit for the virtual service address, causing a degree of granularity of the network segment information in the first routing information to be finer than a degree of granularity of the network segment information in the second routing information, and the first routing information to have a higher priority as compared to the second routing information.
2. The method according to claim 1 , wherein
the configuration information includes the virtual service address configured by the first service unit for the first load balancing task, and
triggering the target service unit to publish the first routing information according to the configuration information of the first service unit for the first load balancing task includes:
triggering the target service unit to publish the first routing information according to the virtual service address, to enable a service request for the virtual service address to be addressed to the target service unit.
3. The method according to claim 2 , wherein triggering the target service unit to publish the first routing information according to the virtual service address comprises:
obtaining the second routing information published by the first service unit for the virtual service address; and
sending the second routing information to the target service unit to trigger the target service unit to publish the first routing information with the higher priority than the second routing information according to the virtual service address and the second routing information.
4. The method according to claim 1 , further comprising:
sending a session sending instruction to the first service unit to trigger the first service unit to send recorded session information about the first load balancing task to the target service unit to allow the target service unit to reference with when distributing service requests related to established connections, wherein the recorded session information includes connection information of the established connections.
5. The method according to claim 4 , wherein the target service unit comprises a cluster composed of a plurality of second service nodes and the sending includes:
sending a session sending instruction to the first service unit to trigger the first service unit to send the recorded session information about the first load balancing task to a target service node among the plurality of second service nodes, the target service node synchronizing the recorded session information with other second service nodes among the plurality of second service nodes.
6. The method according to claim 1 , wherein triggering the target service unit to publish the first routing information according to the configuration information of the first service unit for the first load balancing task comprises:
obtaining the configuration information of the first service unit for the first load balancing task; and
sending the configuration information to the target service unit, to enable the target service unit to complete configuration according to the configuration information, and publish the first routing information according to the configuration information.
7. The method according to claim 6 , wherein sending the configuration information to the target service unit comprises:
sending the configuration information to a target management and control unit corresponding to the target service unit, to allow the target management and control unit to forward the configuration information to the target service unit.
8. The method according to claim 1 , further comprising:
determining the first service unit, the first load balancing task, and the target service unit according to information to be migrated, wherein:
the information to be migrated is determined according to detected operating conditions of multiple service units, the multiple service units including the first service unit and the target service unit; and
the information to be migrated includes a virtual service address configured by the first service unit for the first load balancing task and a service address of the target service unit.
9. The method according to claim 8 , further comprising:
receiving the information to be migrated that is sent by a global dispatching unit and determined according to the detected operating conditions of the multiple service units.
10. The method according to claim 1 , further comprising:
triggering the first service unit to cancel second routing information that has been published for the first load balancing task after receiving a publishing notification about the first routing information.
11. The method according to claim 1 , further comprising:
triggering the first service unit to delete configuration related to the first load balancing task after receiving a publishing notification about the first routing information.
12. The method according to claim 1 , further comprising:
receiving detection information detected by the target service unit for the first load balancing task; and
determining whether the target service unit satisfies a takeover condition according to the detection information, wherein triggering the target service unit to publish the first routing information according to the configuration information of the first service unit for the first load balancing task is performed when the target service unit satisfies the takeover condition.
13. The method according to claim 12 , wherein:
the detection information includes: first health status information obtained by the target service unit by detecting multiple back-end servers, wherein the multiple back-end servers are used to process service requests related to the first load balancing task; and
determining whether the target service unit satisfies the takeover condition according to the detection information includes: determining whether the target service unit satisfies the takeover condition according to the first health status information.
14. The method according to claim 13 , wherein:
the target service unit is a cluster composed of a plurality of second service nodes;
the detection information further includes: an amount of synchronization of session information related to the first load balancing task among the plurality of second service nodes; and
determining whether the target service unit satisfies the takeover condition according to the first health status information includes:
determining whether the target service unit satisfies the takeover condition according to the first health status information and the amount of synchronization, the session information being recorded by the first service unit when providing the traffic distribution service for the first load balancing task.
15. The method according to claim 14 , wherein determining whether the target service unit satisfies the takeover condition according to the first health status information and the amount of synchronization comprises:
obtaining second health status information obtained by the first service unit by detecting of the multiple back-end servers;
determining whether a difference between the first health state detection information and the second health state detection information satisfies a first preset condition;
determining a proportion of the amount of synchronization in a total amount of session information; and
determining that the target service unit satisfies the takeover condition when the difference satisfies the first preset condition and the proportion is greater than a preset proportion.
16. One or more computer readable media storing executable instructions that, when executed by one or more processors, cause the one or more processors to perform acts comprising:
obtaining configuration information of a first service unit for a first load balancing task, the configuration information including a virtual service address configured by the first service unit for the first load balancing task; and
publishing first routing information according to the configuration information, to replace the first service unit to provide a traffic distribution service for the first load balancing task, wherein:
attributes of a connection previously established by the first service unit for the first load balancing task have no change before and after the target service unit takes over the first service unit to provide the traffic distribution service for the first load balancing task;
the first routing information published by the target service unit includes network segment information about the virtual service address; and
a number after a designated symbol in the network segment information in the first routing information is larger than a number after the designated symbol in network segment information in second routing information published by the first service unit for the virtual service address, causing a degree of granularity of the network segment information in the first routing information to be finer than a degree of granularity of the network segment information in the second routing information, and the first routing information to have a higher priority as compared to the second routing information.
17. The one or more computer readable media according to claim 16 , wherein publishing the first routing information according to the configuration information comprises:
obtaining the second routing information that the first service unit has published for the first load balancing task; and
publishing the first routing information with the higher priority than the second routing information according to the configuration information and the second routing information.
18. The one or more computer readable media according to claim 16 , the acts further comprising:
receiving session information about the first load balancing task sent by the first service unit; and
synchronizing the session information with other second service nodes in a cluster, each second service node in the cluster being used to provide traffic distribution services for the first load balancing task.
19. The one or more computer readable media according to claim 18 , the acts further comprising:
sending detection information detected for the first load balancing task to a target management and control unit, to enable the target management and control unit to determine whether a takeover condition is satisfied according to the detection information, wherein publishing the first routing information according to the configuration information is performed after receiving a takeover instruction sent by the target management and control unit upon determining that the takeover condition is satisfied.
20. A system comprising:
one or more processors;
memory;
a first management and control unit stored in the memory and executable by the one or more processors that is configured to determine a target service unit, and trigger the target service unit to publish first routing information according to configuration information of a first service unit for a first load balancing task; and
the target service unit stored in the memory and executable by the one or more processors that is configured to publish the first routing information according to the configuration information upon being triggered by the first management and control unit, to replace the first service unit to provide a traffic distribution service for the first load balancing task, wherein:
attributes of a connection previously established by the first service unit for the first load balancing task have no change before and after the target service unit takes over the first service unit to provide the traffic distribution service for the first load balancing task;
the first routing information published by the target service unit includes network segment information about a virtual service address configured by the first service unit for the first load balancing task; and
a number after a designated symbol in the network segment information in the first routing information is larger than a number after the designated symbol in network segment information in second routing information published by the first service unit for the virtual service address, causing a degree of granularity of the network segment information in the first routing information to be finer than a degree of granularity of the network segment information in the second routing information, and the first routing information to have a higher priority as compared to the second routing information.