CN114760303A

CN114760303A - Traffic configuration, traffic distribution and service program upgrading method for server cluster

Info

Publication number: CN114760303A
Application number: CN202210323799.2A
Authority: CN
Inventors: 范开强
Original assignee: Jingdong Technology Information Technology Co Ltd
Current assignee: Jingdong Technology Information Technology Co Ltd
Priority date: 2022-03-29
Filing date: 2022-03-29
Publication date: 2022-07-15

Abstract

The application provides a method for flow configuration, flow distribution and service program upgrade of a server cluster, which relates to the technical field of computers, wherein the flow configuration method is applied to a shunting configuration server and comprises the following steps: monitoring versions of service programs adopted by a plurality of server clusters; configuring the flow states of the plurality of server clusters according to the versions of the service programs adopted by the plurality of server clusters; and synchronizing the traffic states of the plurality of server clusters to the DNS so that the DNS distributes the traffic to the plurality of server clusters according to the updated traffic states. The flow states of the server clusters are configured according to the versions of the service programs adopted by the server clusters, so that the versions of the service programs providing services in the server clusters can be ensured to be consistent, and the condition that the data of a user terminal is disordered due to the mixed use of new and old versions when the versions of the service programs adopted by the server clusters are upgraded is avoided.

Description

Traffic configuration, traffic distribution and service program upgrading method for server cluster

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method for traffic configuration, traffic distribution, and service program upgrade of a server cluster.

Background

The server cluster is composed of a plurality of server hosts, and the plurality of server hosts have the same functions and are grouped into a group to integrally manage and provide services.

At present, with the rapid development of the internet, the related service traffic also shows explosive growth, and in the related technology, the traffic of a server cluster is generally distributed and controlled by adopting reverse proxy servers such as a Nginx/Apache/Squid server. However, in this way of allocating and controlling traffic, when a service program used by a server cluster is upgraded from an old version to a new version, since the service programs of the new and old versions provide services at the same time, a situation that data confusion of a user end is caused by mixed use of the new and old versions is likely to occur.

Disclosure of Invention

The present application is directed to solving, at least in part, one of the technical problems in the related art.

The application provides a method for flow configuration, flow distribution and service program upgrading of a server cluster, which aims to solve the technical problem that in the flow distribution and control mode in the related technology, when version upgrading is carried out on a service program adopted by the server cluster, due to the fact that service programs of new and old versions provide services at the same time, the situation that user side data are disordered due to the mixed use of the new and old versions is easy to happen.

An embodiment of the first aspect of the present application provides a traffic configuration method for a server cluster, which is applied to a offload configuration server, and includes: monitoring versions of service programs adopted by a plurality of server clusters; configuring the flow states of the plurality of server clusters according to the versions of the service programs adopted by the plurality of server clusters; and synchronizing the traffic states of the plurality of server clusters to a Domain Name System (DNS) server so that the DNS server performs traffic distribution on the plurality of server clusters according to the updated traffic states.

According to the flow configuration method of the server cluster, the flow states of the server clusters are configured according to the versions of the service programs adopted by the server clusters, the versions of the service programs for providing services in the server clusters can be guaranteed to be consistent, and therefore the situation that data of a user terminal is disordered due to the mixed use of new and old versions when the versions of the service programs adopted by the server clusters are upgraded is avoided.

An embodiment of a second aspect of the present application provides a method for allocating traffic of a server cluster, which is applied to a DNS server, and includes: receiving a traffic state synchronized by a traffic configuration server by using the traffic configuration method in the embodiment of the first aspect; and carrying out flow distribution on the plurality of server clusters according to the flow state.

According to the traffic distribution method for the server clusters provided by the embodiment of the application, the traffic distribution is performed on the plurality of server clusters according to the traffic state by receiving the traffic state synchronized by the flow distribution configuration server by using the traffic configuration method of the embodiment of the first aspect, so that the traffic distribution is performed on the plurality of server clusters according to the traffic state synchronized by the flow distribution configuration server.

An embodiment of a third aspect of the present application provides a method for upgrading a service program of a server cluster, which is applied to the server cluster, and includes: monitoring traffic distributed by a DNS server to determine the state of the server cluster; wherein, the traffic is obtained by the DNS server distributing traffic states synchronized by the traffic distribution configuration server according to the traffic distribution configuration method described in the embodiment of the first aspect; and upgrading the version of the service program according to the state of the server cluster.

According to the method for upgrading the service program of the server cluster, the state of the server cluster is determined by monitoring the flow distributed by the DNS, the version of the service program is upgraded according to the state of the server cluster, the version of the service program of the server cluster is upgraded, and the condition that data of a user terminal is disordered due to mixed use of new and old versions when the version of the service program adopted by the server cluster is upgraded is avoided.

An embodiment of a fourth aspect of the present application provides a stream configuration server, including: the monitoring module is used for monitoring the versions of the service programs adopted by the plurality of server clusters; the configuration module is used for configuring the flow states of the plurality of server clusters according to the versions of the service programs adopted by the plurality of server clusters; and the synchronization module is used for synchronizing the traffic states of the plurality of server clusters to a Domain Name System (DNS) server so as to enable the DNS server to distribute the traffic of the plurality of server clusters according to the updated traffic states.

According to the distribution configuration server, the flow states of the server clusters are configured according to the versions of the service programs adopted by the server clusters, the versions of the service programs for providing services in the server clusters can be guaranteed to be consistent, and therefore the situation that data of a user terminal is disordered due to the mixed use of new and old versions when the versions of the service programs adopted by the server clusters are upgraded is avoided.

An embodiment of a fifth aspect of the present application provides a DNS server, including: a receiving module, configured to receive a traffic state synchronized by the offloading configuration server by using the traffic configuration method according to the embodiment of the first aspect; and the distribution module is used for carrying out flow distribution on the plurality of server clusters according to the flow state.

The DNS server provided in the embodiment of the present application receives the traffic state synchronized by the flow distribution configuration server using the traffic configuration method according to the embodiment of the first aspect, and performs traffic distribution on the plurality of server clusters according to the traffic state, thereby implementing traffic distribution on the plurality of server clusters according to the traffic state synchronized by the flow distribution configuration server.

An embodiment of a sixth aspect of the present application provides a server cluster, including: the monitoring module is used for monitoring the flow distributed by the DNS server so as to determine the state of the server cluster; wherein, the traffic is obtained by the DNS server distributing traffic states synchronized by the flow configuration method according to the embodiment of the first aspect; and the upgrading module is used for upgrading the version of the service program according to the state of the server cluster.

The server cluster provided by the embodiment of the application determines the state of the server cluster by monitoring the flow distributed by the DNS, and performs version upgrade of the service program according to the state of the server cluster, so that the version upgrade of the service program of the server cluster is realized, and the condition that the data of a user terminal is disordered due to mixed use of new and old versions when the version upgrade of the service program adopted by the server cluster is performed is avoided.

An embodiment of a seventh aspect of the present application provides a traffic configuration system for a server cluster, including a plurality of server clusters for executing the service program upgrading method according to the embodiment of the third aspect; a flow distribution configuration server configured to execute the traffic configuration method according to the embodiment of the first aspect, so as to configure traffic states of a plurality of server clusters; and a DNS server configured to execute the traffic distribution method according to the embodiment of the second aspect, so as to perform traffic distribution on a plurality of server clusters.

An embodiment of an eighth aspect of the present application provides an electronic device, including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executable by the at least one processor to enable the at least one processor to perform the method as set forth in the embodiments of the first aspect, the embodiments of the second aspect, or the embodiments of the third aspect of the present application.

A ninth aspect of the present application proposes a non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform the method as set forth in the first or second or third aspect of the present application.

A tenth aspect of the present application provides a computer program product, comprising a computer program, which when executed by a processor, implements the method as set forth in the first aspect of the present application, or in the second aspect of the present application, or in the third aspect of the present application.

Additional aspects and advantages of the present application will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the present application.

Drawings

The foregoing and/or additional aspects and advantages of the present application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:

fig. 1 is a schematic flowchart of a traffic configuration method for a server cluster according to an embodiment of the present application;

fig. 2 is another schematic flow chart of a traffic configuration method for a server cluster according to an embodiment of the present application;

fig. 3 is a normal traffic distribution diagram of a server cluster a and a server cluster B provided in the embodiment of the present application;

fig. 4 is a flow distribution diagram of a server cluster a and a server cluster B in a first flow state according to the embodiment of the present application;

fig. 5 is another traffic distribution diagram of the server cluster a and the server cluster B in the first traffic state according to the embodiment of the present application;

Fig. 6 is a traffic distribution diagram of a server cluster a and a server cluster B in a second traffic state according to the embodiment of the present application;

fig. 7 is another traffic distribution diagram of the server cluster a and the server cluster B in the second traffic state according to the embodiment of the present application;

fig. 8 is a further flow distribution diagram of the server cluster a and the server cluster B in the second flow state according to the embodiment of the present application;

fig. 9 is a flow distribution diagram of a server cluster a and a server cluster B in a third flow state according to the embodiment of the present application;

fig. 10 is a schematic flowchart of a traffic distribution method for a server cluster according to an embodiment of the present application;

fig. 11 is a schematic flowchart of a method for upgrading a service program of a server cluster according to an embodiment of the present application;

fig. 12 is another schematic flowchart of a method for upgrading a service program of a server cluster according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of a offloading configuration server according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of a DNS server according to an embodiment of the present application;

fig. 15 is a schematic structural diagram of a server cluster provided in the embodiment of the present application;

FIG. 16 illustrates a block diagram of an exemplary electronic device suitable for use in implementing embodiments of the present application.

Detailed Description

Reference will now be made in detail to the embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are illustrative and intended to explain the present application and should not be construed as limiting the present application.

At present, with the rapid development of the internet, the related service traffic also shows explosive growth, and in the related technology, the traffic of a server cluster is generally distributed and controlled by using reverse proxy servers such as a Nginx/Apache/Squid server. However, in this way of traffic distribution and control, when the service program adopted by the server cluster is upgraded from the old version to the new version, because the service programs of the new and old versions provide services at the same time, the situation that the data of the user terminal is confused due to the mixed use of the new and old versions is likely to occur.

For example, when the service program adopted by the server cluster a is upgraded from an old version to a new version, the service program of the new version of the server cluster a provides service, and for the server cluster B which is not upgraded with the version of the service program, the service program of the old version provides service, and since the service programs of the new and old versions provide service at the same time, when the user side realizes a certain function through the service programs of the server cluster a and the server cluster B, the situation of data confusion of the user side is easy to occur.

The present application mainly addresses the above technical problems, and provides a traffic configuration method, a traffic distribution method, a service program upgrade method, a traffic distribution server, a DNS (Domain Name System) server, a server cluster, a traffic configuration System of the server cluster, an electronic device, a storage medium, and a computer program product, which can avoid a situation in which user-side data is disturbed due to mixed use of new and old versions when a version of a service program used by the server cluster is upgraded.

A traffic configuration method, a traffic distribution method, a service program upgrade method, a traffic distribution configuration server, a DNS server, a server cluster, a traffic configuration system of a server cluster, an electronic device, a storage medium, and a computer program product of a server cluster according to embodiments of the present application are described below with reference to the accompanying drawings.

In order to clearly explain the technical solutions provided in the embodiments of the present application, first, the offloading configuration server and the related terms provided in the embodiments of the present application are explained.

The distribution configuration server has the following functions: configuring each server cluster to be in an enabling state or a disabling state, and configuring the effective version of the service program adopted by each server cluster. Moreover, the flow distribution configuration server can synchronize the flow states of the configured multiple server clusters to the DNS server, and synchronize the effective versions of the service programs adopted by the configured server clusters to the corresponding server clusters.

Among them, the DNS server, which is a service provided for the Internet, serves as a distributed database in which domain names and IP (Internet Protocol) addresses are mapped to each other, enabling a person to more conveniently access the Internet. For example, the DNS server can map the website http:// xiaozhi. 1.2.3.4.

Referring to table 1, the offload configuration server may configure server cluster a and server cluster B to be in an enabled state. In the column "IP list" in table 1, "1.2.3.4" and "2.3.4.5" respectively indicate IP addresses of different server hosts in server cluster a, and "5.6.7.8" and "9.0.1.2" respectively indicate IP addresses of different server hosts in server cluster B. In the "cluster identification" column in table 1, "Jimi 1" and "Jimi 2" represent the identification of server cluster a and server cluster B, respectively, the identification of the server cluster, for uniquely identifying the server cluster.

Table 1 traffic configuration for a cluster of servers

It should be noted that, for a server cluster in an enabled state, a DNS server will allocate traffic to the server cluster, that is, when a client (also referred to as a user side in this embodiment) where a user is located accesses a certain website, the DNS server will return an IP address of the server cluster to the client, so that the server cluster can provide service for the client to access the website; for the server cluster in the disabled state, the DNS server does not distribute traffic to the server cluster, that is, when the client where the user is located accesses a certain website, the DNS server does not return the IP address of the server cluster to the client, so that the server cluster does not provide service for the client to access the website. The traffic may be understood as http (hypertext Transfer Protocol) or https (hypertext Transfer Protocol over Secure Socket Layer) traffic provided for a user to access a specified domain address through a browser when the user uses a service of a service program of a server cluster through the browser.

Referring to table 2, the offloading configuration server may further configure whether each version of the service program used by the server cluster a and the server cluster B is in an effective state. When a certain version is in a valid state, the version is called as a valid version. In the "version number" column in table 2, "20210619010100" and "20210618010100" respectively indicate the version number of the service program employed by the server cluster. A version number for uniquely identifying the version of the service program.

TABLE 2 version configuration of servlets for a server cluster

Cluster identification	Cluster name	Version number	Whether or not it is effective
				Jimi1	Cluster A	20210619010100	Is effective
Jimi1	Cluster A	20210618010100	Invalidation
				Jimi2	Cluster B	20210619010100	Is effective
Jimi2	Cluster B	20210618010100	Invalidation

It should be noted that the service program adopted by each server cluster has only one valid version, the remaining versions are to-be-generated state, and there may be a plurality of versions in to-be-generated state, which is not limited in the present application. For the effective version of the service program of the server cluster, when the client where the user is located accesses the IP address of the server cluster, the server cluster returns the version number corresponding to the effective version to the client through a Web (World Wide Web) home page by using the version acquisition component installed in the server cluster, so that the client loads the specific content and service of the effective version from the server cluster by using the version number. The version obtaining component is an SDK (Software Development Kit) in the server cluster, and the SDK runs in each server host of the server cluster. The web home page is a web page which is entered for the first time by a client side where a user is located and using functions provided by the server cluster through flow.

First, a traffic configuration method of a server cluster provided in the embodiment of the present application is described below. The traffic configuration method for the server cluster provided by the embodiment of the present application is configured to be executed in a flow distribution configuration server.

Fig. 1 is a schematic flowchart of a traffic configuration method for a server cluster according to an embodiment of the present disclosure.

As shown in fig. 1, the traffic configuration method for the server cluster may include the following steps 101-103.

Step 101, monitoring versions of service programs adopted by a plurality of server clusters.

The service program refers to a specific program in the server cluster, which provides services for a user when the user accesses a specific webpage through a browser. The version of the service program can be updated as required, and after the version of the service program is updated, the user side refreshes the browser to experience a new version and service.

In an exemplary embodiment, the offloading configuration server may monitor whether versions of service programs adopted by the multiple server clusters need to be upgraded, whether the versions are upgraded from an old version to a new version (in this embodiment, the old version is referred to as a first version, and the new version is referred to as a second version), which version the effective version of the service program in each server cluster is, and the like.

Step 102, configuring the flow states of the plurality of server clusters according to the versions of the service programs adopted by the plurality of server clusters.

In an exemplary embodiment, the offload configuration server may configure traffic states of the multiple server clusters according to versions of service programs adopted by the multiple server clusters. For example, when a target server cluster in the multiple server clusters needs to be version-upgraded, the offloading configuration server may configure the target server cluster in the disabled state, and the remaining server clusters in the enabled state.

And 103, synchronizing the traffic states of the plurality of server clusters to the domain name system DNS server so that the domain name system DNS server performs traffic distribution on the plurality of server clusters according to the updated traffic states.

In an exemplary embodiment, after the offloading configuration server configures traffic states of multiple server clusters, the traffic states of the multiple server clusters may be synchronized to a domain name system DNS server, so that the domain name system DNS server performs traffic allocation on the multiple server clusters according to the updated traffic states.

For example, assume that the traffic states of the multiple server clusters configured by the offload configuration server are: when a client of a user accesses a certain website, the DNS server returns IP addresses of the rest server clusters corresponding to the website to the client and does not return the IP addresses of the target server clusters corresponding to the website any more, so that only the rest server clusters in the plurality of server clusters provide services when the target server clusters perform version upgrade, and because the versions of service programs in the rest server clusters are consistent, the versions of the service programs providing services in the plurality of server clusters can be ensured to be consistent, and the service programs adopted by the server clusters are prevented from being used for version upgrade, the condition of data confusion of the user end caused by the mixed use of the new version and the old version can not interrupt the service of the user.

According to the traffic configuration method of the server cluster, the versions of the service programs adopted by the plurality of server clusters are monitored, the traffic states of the plurality of server clusters are configured according to the versions of the service programs adopted by the plurality of server clusters, and the traffic states of the plurality of server clusters are synchronized to the DNS server, so that the DNS server performs traffic distribution on the plurality of server clusters according to the updated traffic states.

The following further describes a traffic configuration method of a server cluster in this embodiment with reference to fig. 2.

Fig. 2 is a schematic flowchart of a traffic configuration method for a server cluster according to an embodiment of the present disclosure. As shown in fig. 2, the traffic configuration method for the server cluster includes the following

steps

201 and 205.

Step 201, monitoring versions of service programs adopted by a plurality of server clusters.

For a specific implementation process and principle of step 201, reference may be made to the description of the foregoing embodiments, which are not described herein again.

It should be noted that, during the process of upgrading the service program by the multiple server clusters, the offloading configuration server may continuously monitor or monitor the versions of the service programs adopted by the multiple server clusters at preset time intervals until the upgrading of the versions of the service programs adopted by the multiple server clusters is finished. The preset time interval may be set as needed, and the embodiment of the present application does not limit this.

Step 202, under the condition that a service program of a target server cluster in a plurality of server clusters needs to be subjected to version upgrading, configuring the plurality of server clusters to be in a first flow state; the target server cluster is in a disabled state in the first traffic state, and the rest of the plurality of server clusters are in an enabled state.

The number of the target server clusters may be one or multiple, which is not limited in the present application. For example, when the plurality of server clusters all need to perform version upgrade of the service program, the number of the target server clusters may be set to perform version upgrade of the service program on half of the server clusters, and after the version upgrade of the service program of the server clusters, the number of the target server clusters is set to be half of the number of the server clusters. In the following embodiments of the present application, a description is given by taking an example that the plurality of server clusters include two server clusters, namely, a server cluster a and a server cluster B.

In an exemplary embodiment, when a service program of a target server cluster in a plurality of server clusters needs to be version-upgraded, after a offload server configures the plurality of server clusters to a first traffic state, the first traffic state may be synchronized to a DNS server, so that the DNS server performs traffic distribution on the plurality of server clusters according to an updated traffic state.

Referring to the normal traffic distribution diagram of the server cluster a and the server cluster B shown in fig. 3, before the server cluster a and the server cluster B do not perform version upgrade on the service program, both the server cluster a and the server cluster B are in an enabled state. In the traffic state, the DNS server will distribute traffic to the server cluster a and the server cluster B, and when a client where a user is located accesses a certain web page through a browser, the client may query the IP address of the web address for the server cluster (step 301), and the DNS server may poll the IP address of the server cluster a or the server cluster B returned to the client, so that the client may access the corresponding server cluster a or the corresponding server cluster B through the browser (step 302). Taking the IP address of the server cluster a returned by the DNS server to the client as an example, the version obtaining component SDK in the server cluster a may read the version number corresponding to the validated version of the server cluster a (step 303), and respond to the home page of the specified version (the validated version of the service program of the server cluster a) (step 304), where the home page includes the version number corresponding to the validated version of the service program of the server cluster a, and then the client may automatically load the content and function of the validated version in the server cluster a by using the version number in the home page (step 305).

Assuming that the server cluster B is a target server cluster requiring version upgrade, the offloading configuration server may configure the server cluster a and the server cluster B to be in the first traffic state under the condition that the offloading configuration server determines that the service program of the server cluster B requires version upgrade. In the first traffic state, the target server cluster, i.e., the server cluster B, is in a disabled state, and the remaining server clusters, i.e., the server cluster a, are in an enabled state. And, the offloading configuration server may synchronize traffic states of the server cluster a and the server cluster B to the DNS server, so that the DNS server allocates traffic to the server cluster a.

Referring to fig. 4, a traffic distribution diagram of server cluster a and server cluster B in a first traffic state is shown, where server cluster a is in an enabled state and server cluster B is in a disabled state. In the first traffic state, the DNS server will allocate traffic to the server cluster a, and when a client where the user is located accesses a certain web page through a browser, the DNS server may query an IP address of the web address for the server cluster a (step 401), and the DNS server may return the IP address of the server cluster a to the client, so that the client may access the corresponding server cluster a through the browser (step 402). The version obtaining component SDK in the server cluster a may read a version number corresponding to the effective version of the server cluster a (step 403), and respond to a home page of a specified version (the effective version of the service program of the server cluster a) (step 404), where the home page includes the version number corresponding to the effective version of the service program of the server cluster a, and then the client may automatically load the content and function of the effective version in the server cluster a by using the version number in the home page (step 405).

It should be noted that, in the SDK in each traffic distribution map in the embodiment of the present application, the version obtaining component SDK in the server cluster is a version obtaining component SDK, and the version obtaining component SDK runs in each server host of the server cluster.

Step 203, under the condition that the service program of the target server cluster in the forbidden state in the plurality of server clusters is upgraded from the first version to the second version and the effective version of the service program is the first version, configuring the plurality of server clusters to be switched from the first flow state to the second flow state; and the target server cluster is in an enabled state under the second traffic state, and the rest server clusters are in a disabled state.

In an exemplary embodiment, when the plurality of server clusters are in the first traffic state, the target server cluster in the disabled state may perform version upgrade of the service program to upgrade from the first version to the second version, and the target server cluster may switch the first version to the valid state according to the configuration of the offload configuration server for the valid version of the target server cluster.

Referring to fig. 5, a traffic distribution diagram of server cluster a and server cluster B in a first traffic state is shown, where server cluster a is in an enabled state and server cluster B is in a disabled state. In the first traffic state, the process (step 501-505) when the client accesses a certain webpage through the browser is similar to the process (step 401-405) shown in fig. 4, and will not be described herein again. When the server cluster a and the server cluster B are in the first traffic state, the server cluster B may upgrade the version of the service program, and after the service program of the server cluster B is upgraded from the first version corresponding to the version number "20210619010100" to the second version corresponding to the version number "20210620010100", the first version corresponding to the version number "20210619010100" before upgrading may be switched to an effective state according to the configuration of the offload configuration server to the effective version of the server cluster B.

When the service program of the target server cluster in the disabled state in the multiple server clusters is upgraded from the first version to the second version, and the effective version of the service program is the first version, the offloading configuration server may configure the multiple server clusters to be switched from the first traffic state to the second traffic state. And the target server cluster is in an enabled state under the second traffic state, and the rest server clusters are in a disabled state. And the offloading configuration server may synchronize the second traffic state to the DNS server, so that the DNS server performs traffic allocation on the multiple server clusters according to the updated traffic state.

Referring to fig. 6, a traffic distribution diagram of server cluster a and server cluster B in a second traffic state is shown, where server cluster a is disabled and server cluster B is enabled. In the second traffic state, the DNS server will allocate traffic to the server cluster B, and when the client where the user is located accesses a certain web page through the browser, the DNS server may query the IP address of the web address corresponding to the server cluster B (step 601), and the DNS server may return the IP address of the server cluster B to the client, so that the client may access the corresponding server cluster B through the browser (step 602). The version obtaining component SDK in the server cluster B may read a version number corresponding to the validated version of the server cluster B (step 603), and respond to a home page of a specified version (the validated version of the service program of the server cluster B) (step 604), where the home page includes the version number corresponding to the validated version of the service program of the server cluster B, and then the client may automatically load the content and function of the validated version in the server cluster B according to the version number in the home page (step 605).

By the analysis, after the service program of the target server cluster is upgraded from the first version to the second version, the effective version of the service program can be switched to the first version according to the configuration of the shunting configuration server on the effective version of the target server cluster. Correspondingly, before configuring the plurality of server clusters to switch from the first traffic state to the second traffic state, the offloading configuration server may further include the following steps:

configuring the effective version of the service program in the target server cluster as a first version;

and sending the first version configuration message to the target server cluster so that the target server switches the effective version of the service program according to the first version configuration message.

The first version configuration message is used for indicating that the effective version of the service program in the target server cluster is the first version.

Step 204, under the condition that the effective version of the service program in the target server cluster is switched from the first version to the second version, the service programs in the rest server clusters are upgraded from the first version to the second version, and the effective versions of the service programs in the rest server clusters are the second versions, configuring a plurality of server clusters to be switched from the second flow state to the third flow state; and the target server cluster and the rest server clusters are in the starting state in the third flow state.

In an exemplary embodiment, in a second traffic state of the plurality of server clusters, the target server cluster in the enabled state may switch the effective version of the service program of the target server cluster from the first version to the second version according to the configuration of the offload configuration server for the effective version of the target server cluster, and the remaining server clusters in the disabled state may perform version upgrade of the service program to upgrade from the first version to the second version, and the remaining server clusters may switch the second version to the effective state according to the configuration of the offload configuration server for the effective version of the remaining server clusters. The switching process of the effective version of the service program of the target server cluster, the version upgrading process of the service program of the other servers, and the switching process of the effective version may be executed at the same time or at different times, which is not limited in the present application.

Referring to fig. 7, the traffic distribution diagram of server cluster a and server cluster B in the second traffic state is shown, where server cluster a is disabled and server cluster B is enabled. In the second traffic state, the process (step 701-705) when the client accesses a certain webpage through the browser is similar to the process (step 601-605) shown in fig. 6, and will not be described herein again. When the server cluster a and the server cluster B are in the second traffic state, the server cluster B may switch the effective version of the service program of the server cluster B from the first version corresponding to the version number "20210619010100" to the second version corresponding to the version number "20210620010100" according to the configuration of the offload configuration server on the effective version of the server cluster B.

Referring to the traffic distribution diagram of the server cluster a and the server cluster B shown in fig. 8 in the second traffic state, the server cluster a may upgrade the version of the service program, and after the service program of the server cluster a is upgraded from the first version corresponding to the version number "20210619010100" to the second version corresponding to the version number "20210620010100", the second version corresponding to the version number "20210620010100" may be switched to the valid state according to the configuration of the offload configuration server to the valid version of the server cluster a.

Under the condition that the effective version of the service programs in the target server cluster is switched from the first version to the second version, the service programs in the rest server clusters are upgraded from the first version to the second version, and the effective versions of the service programs in the rest server clusters are the second version, the shunting configuration server can configure the plurality of server clusters to be switched from the second flow state to the third flow state; and the target server cluster and the rest server clusters are in the starting state in the third flow state. And the offloading configuration server may synchronize the third traffic state to the DNS server, so that the DNS server performs traffic allocation on the multiple server clusters according to the updated traffic state.

Referring to the traffic profiles of server cluster a and server cluster B in the third traffic state shown in fig. 9, server cluster a and server cluster B are both enabled. In the third traffic state, the DNS server will distribute the traffic to the server cluster a and the server cluster B, and the process (step 901 and 905) when the client accesses a certain web page through the browser is similar to the process (step 301 and 305) shown in fig. 3, and will not be described herein again.

As can be seen from the traffic profiles of the server cluster a and the server cluster B in the first traffic state, the second traffic state, and the third traffic state shown in fig. 3 to 9, in the first traffic state of the server cluster a and the server cluster B, only the first version of the server program of the server cluster a provides service in the server cluster a and the server cluster B; when the server cluster A and the server cluster B are in the second traffic state and the effective version of the service program of the server cluster B is the first version, only the service program of the first version of the server cluster B in the server cluster A and the server cluster B provides service; when the server cluster A and the server cluster B are in a second flow state and the effective version of the service program of the server cluster B is a second version, only the service program of the second version of the server cluster B in the server cluster A and the server cluster B provides service; and under the third flow state of the server cluster A and the server cluster B, the service program of the second version of the server cluster A and the service program of the second version of the server cluster B provide services. That is to say, the traffic configuration method for the server cluster provided by the embodiment of the application can ensure that the versions of the service programs providing services in the plurality of server clusters are consistent, thereby avoiding the occurrence of data confusion of the user end due to mixed use of new and old versions when the versions of the service programs adopted by the server clusters are upgraded.

Through the analysis, the target server cluster can switch the effective version of the service program from the first version to the second version according to the configuration of the shunting configuration server on the effective version of the target server cluster. Correspondingly, in an exemplary embodiment, before configuring the plurality of server clusters to switch from the second traffic state to the third traffic state, the offloading configuration server may further include the following steps:

configuring the effective version of the service program in the target server cluster as a second version;

and sending a second version configuration message to the target server cluster so that the target server switches the effective version of the service program according to the second version configuration message.

And the second version configuration message is used for indicating that the effective version of the service program in the target server cluster is the second version.

In addition, the other server clusters need to switch the effective version of the service program to the second version according to the configuration of the shunting configuration server on the effective version of the other server clusters. Correspondingly, before configuring the plurality of server clusters to switch from the second flow state to the third flow state, the offloading configuration server may further include the following steps:

Configuring the effective versions of the service programs in the rest server clusters as second versions;

and sending a third version configuration message to the rest server clusters so that the rest servers switch the effective versions of the service programs according to the third version configuration message.

And the third version configuration message is used for indicating that the effective version of the service programs in the rest server clusters is the second version.

The effective version of the service program in the target server cluster and the effective versions of the service programs in the other server clusters are configured through the shunting configuration server, and the version configuration message is sent to the target server cluster or the other server clusters, so that each server cluster can switch the effective versions of the service programs according to the version configuration message sent by the shunting configuration server.

Step 205, synchronizing the traffic states of the multiple server clusters to the DNS server, so that the DNS server performs traffic distribution on the multiple server clusters according to the updated traffic states.

In an exemplary embodiment, the traffic states of the multiple server clusters may be synchronized to the DNS server by the offload configuration server each time the traffic states of the multiple server clusters are configured. For example, after configuring the plurality of server clusters to be in the first traffic state, the first traffic state may be synchronized to the DNS server, so that the DNS server allocates traffic to the remaining server clusters according to the updated first traffic state. After configuring the plurality of server clusters to the second traffic state, the second traffic state may be synchronized to the DNS server, so that the DNS server allocates traffic to the target server cluster according to the updated second traffic state. After configuring the plurality of server clusters to be in the third flow state, the third flow state may be synchronized to the DNS server, so that the DNS server allocates the traffic to the target server cluster and the remaining server clusters according to the updated third flow state.

It should be noted that, due to the hierarchical and regional cache of the DNS server, after the traffic state of the multiple server clusters is synchronized to the DNS server by the offloading configuration server, there may be a delay in traffic allocation of the DNS server to the multiple server clusters, that is, the traffic of the multiple server clusters may reach the traffic state synchronized by the offloading configuration server after a period of delay, and when the traffic of the multiple server clusters reaches the traffic state synchronized by the offloading configuration server, the traffic state synchronization of the multiple server clusters is said to be successful. In this embodiment of the application, after synchronizing the traffic states of the plurality of server clusters to the DNS server, the offloading configuration server may further determine whether the traffic state synchronization of the plurality of server clusters is successful. That is, after step 205, the following steps may be further included:

respectively acquiring monitored flow in a plurality of server clusters;

and determining whether the traffic state synchronization of the plurality of server clusters is successful according to the traffic of each server cluster.

In an exemplary embodiment, each server cluster may monitor traffic of the server cluster through the SDK installed therein, and feed back the monitored traffic of the server cluster to the offloading configuration server, so that the offloading configuration server may obtain the monitored traffic of the plurality of server clusters, and further determine whether the traffic state synchronization of the plurality of server clusters is successful according to the traffic of each server cluster.

For example, after the offloading configuration server synchronizes the first traffic state to the DNS server, the traffic monitored in the multiple server clusters may be obtained, and when the offloading configuration server determines that the traffic of the target server cluster is 0 and the traffic of the remaining server clusters is not 0, it may be determined that the first traffic state synchronization is successful; after the shunting configuration server synchronizes the second traffic state to the DNS server, traffic monitored in the plurality of server clusters may be obtained, and when the shunting configuration server determines that the traffic of the target server cluster is not 0 and the traffic of the remaining server clusters is 0, it may be determined that the second traffic state synchronization is successful; after the offloading configuration server synchronizes the third flow state to the DNS server, the flows monitored in the plurality of server clusters may be obtained, and when the offloading configuration server determines that the flow of the target server cluster is not 0 and the flows of the remaining server clusters are not 0, it may be determined that the third flow state synchronization is successful.

In addition, in a possible implementation form of the present application, the offloading configuration server may determine, according to monitoring of versions of service programs adopted by the multiple server clusters, that the service program of a target server cluster in the multiple server clusters has been upgraded from the first version to the second version and an effective version of the target server cluster is the first version, or determine that the effective version of the service program in the target server cluster is switched from the first version to the second version, that the service programs in the remaining server clusters are upgraded from the first version to the second version, and that the effective version of the service programs in the remaining server clusters is the second version.

Correspondingly, step 201 may specifically include:

receiving a version upgrading message fed back by a plurality of server clusters, wherein the version upgrading message is used for indicating that the server clusters upgrade the service programs from a first version to a second version;

and/or receiving a version validation message fed back by the plurality of server clusters, wherein the version validation message is used for indicating the validated version of the service program of the server cluster.

By receiving the version upgrading messages and/or the version validation messages fed back by the plurality of server clusters, the shunting configuration server can determine version upgrading conditions, validation version conditions and other service program version related conditions of the service programs in the plurality of server clusters, so that the flow states of the plurality of server clusters can be configured according to the version related conditions of the service programs adopted by the plurality of server clusters.

In summary, the traffic configuration method for the server cluster can ensure that the versions of the service programs providing services in the plurality of server clusters are consistent, thereby avoiding the occurrence of data confusion of the user end due to mixed use of new and old versions when the versions of the service programs adopted by the server clusters are upgraded.

The following describes a traffic distribution method for a server cluster provided in an embodiment of the present application. The traffic distribution method for the server cluster provided by the embodiment of the application is configured to be executed in a DNS server.

Fig. 10 is a schematic flow chart of a traffic distribution method for a server cluster according to an embodiment of the present application.

As shown in fig. 10, the traffic distribution method of the server cluster may include the following

steps

1001 and 1002.

Step 1001, receiving a traffic state synchronized by the offload configuration server.

The traffic state synchronized by the offloading configuration server is configured by using the traffic configuration method for the server cluster in the embodiment of the first aspect.

Step 1002, performing traffic distribution on the plurality of server clusters according to the traffic state.

In an exemplary embodiment, the offloading configuration server may configure traffic states of the multiple server clusters by using the traffic configuration method for the server clusters described in the above embodiment, and synchronize the traffic states of the multiple server clusters to the DNS server, so that the DNS server may receive the traffic states synchronized by the offloading configuration server, and further perform traffic distribution on the multiple server clusters according to the traffic states.

In an exemplary embodiment, when the traffic state synchronized by the offloading configuration server is a first traffic state (a target server cluster in the plurality of server clusters is in a disabled state, and the remaining server clusters are in an enabled state), the DNS server may allocate the traffic to the remaining server clusters in the enabled state; when the traffic state synchronized by the offloading configuration server is a second traffic state (a target server cluster in the multiple server clusters is in an enabled state, and the remaining server clusters are in a disabled state), the DNS server may allocate the traffic to the target server cluster in the enabled state; when the traffic state synchronized by the offloading configuration server is a third traffic state (a target server cluster and the remaining server clusters in the multiple server clusters are in an enabled state), the DNS server may allocate the traffic to the target server cluster and the remaining server clusters in the enabled state.

According to the traffic distribution method for the server clusters provided by the embodiment of the application, the traffic distribution is performed on the plurality of server clusters according to the traffic state by receiving the traffic state synchronized by the flow distribution configuration server by using the traffic configuration method in the embodiment of the first aspect, so that the traffic distribution is performed on the plurality of server clusters according to the traffic state synchronized by the flow distribution configuration server.

The following describes a service program upgrading method for a server cluster provided in an embodiment of the present application.

Fig. 11 is a flowchart illustrating a service program upgrading method for a server cluster according to an embodiment of the present application. The method for upgrading the service program of the server cluster provided by the embodiment of the application is configured in the server cluster to be executed.

As shown in fig. 11, the method for upgrading a service program of a server cluster provided in the embodiment of the present application includes the following steps 1101-1102.

It should be noted that the server cluster in the embodiment of the present disclosure may be any one of the server clusters in the foregoing embodiments.

At step 1101, the traffic allocated by the DNS server is monitored to determine the status of the server cluster.

The traffic is obtained by the DNS server distributing traffic states synchronized by the traffic configuration method of the server cluster in the embodiment of the first aspect according to the split configuration server.

The state of the server cluster indicates whether the server cluster is enabled, and the state of the server cluster may include an enabled state and a disabled state.

In an exemplary embodiment, the offloading configuration server may configure traffic states of the multiple server clusters by using the traffic configuration method for the server clusters described in the above embodiment, and synchronize the traffic states of the multiple server clusters to the DNS server, so that the DNS server may receive the traffic states synchronized by the offloading configuration server, and further perform traffic distribution on the multiple server clusters according to the traffic states. Each server cluster of the plurality of server clusters may monitor traffic allocated by the DNS server to determine a status of the server cluster.

In an exemplary embodiment, for each server cluster, a version acquisition component SDK is installed in the server cluster, and the server cluster may monitor traffic of the server cluster through the version acquisition component SDK installed therein, and further determine a state of the server cluster according to the traffic of the server cluster. When the flow of the server cluster is 0, determining that the server cluster is in a forbidden state; when the traffic of the server cluster is not 0, it may be determined that the server cluster is in an enabled state.

Step 1102, upgrading the version of the service program according to the state of the server cluster.

In an exemplary embodiment, when the state of the server cluster is the disabled state, the version upgrade of the service program, such as from the first version to the second version, may be performed, and when the state of the server cluster is the enabled state, the version upgrade of the service program may not be performed.

Taking the server cluster in the embodiment of the present application as an example of any one of the target server clusters in the plurality of server clusters in the above embodiments, when the plurality of server clusters are in the first traffic state, that is, when the target server cluster is in the disabled state, the target server cluster may upgrade the service program from the first version to the second version.

Taking the server cluster in this embodiment as any one of the rest server clusters in the multiple server clusters in the foregoing embodiment as an example, when the multiple server clusters are in the second traffic state, that is, when the rest server clusters are in the disabled state, the rest server clusters may upgrade the service program from the first version to the second version.

The server cluster is used for upgrading the version of the service program according to the state, so that the version of the service program can be upgraded only when the service program of the server cluster does not provide service, the versions of the service programs providing service in a plurality of server clusters are consistent, and the condition that the data of a user end is disordered due to mixed use of new and old versions when the version of the service program adopted by the server cluster is upgraded is avoided.

In summary, the method for upgrading the service program of the server cluster provided in the embodiment of the present application determines the state of the server cluster by monitoring the traffic allocated by the DNS server, and performs version upgrading on the service program according to the state of the server cluster, so that the version upgrading on the service program of the server cluster is implemented, and the occurrence of data confusion at the user end due to mixed use of new and old versions when the version upgrading is performed on the service program adopted by the server cluster is avoided.

The service program upgrading method for a server cluster provided in the embodiment of the present application is further described below with reference to fig. 12. The method for upgrading the service program of the server cluster provided by the embodiment of the application is configured in the server cluster to be executed.

Fig. 12 is a schematic flowchart of a method for upgrading a service program of a server cluster according to an embodiment of the present application.

As shown in fig. 12, the method for upgrading a service program of a server cluster may include the following

steps

1201 and 1203.

Step 1201, monitoring the flow rate distributed by the DNS server to determine the state of the server cluster.

Step 1202, upgrading a service program adopted by the server cluster from the first version to the second version under the condition that the state of the server cluster is the forbidden state.

The specific implementation process and principle of steps 1201-1202 may refer to the description of the above embodiments, and are not described herein again.

Step 1203, feeding back a version upgrading message to the offload configuration server, where the version upgrading message is used to indicate that the server cluster has upgraded the service program from the first version to the second version.

In an exemplary embodiment, after the server cluster upgrades the service program from the first version to the second version, a version upgrade message may be fed back to the offload configuration server, so that the offload configuration server may determine that the server cluster has upgraded the service program from the first version to the second version according to the version upgrade message fed back by the server cluster.

It can be understood that, after the service program of the server cluster is upgraded from the first version to the second version, the effective version of the service program may be the first version or the second version. In an exemplary embodiment, the server cluster may switch the first version to the effective version or switch the second version to the effective version according to the configuration of the offload configuration server on the effective version of the service program of the server cluster. Correspondingly, after step 1202, the method may further include:

receiving a version configuration message sent by a shunting configuration server;

and switching the effective version of the service program according to the version configuration message.

The version configuration message is used for indicating the specific effective version of the service program in the server cluster.

Specifically, the offloading configuration server may configure, as needed, which version the effective version of the service program in the server cluster is specific to, and send a version configuration message to the server cluster. Correspondingly, the server cluster can receive the version configuration message sent by the shunting configuration server, and then switch the effective version of the service program according to the version configuration message.

Further, after the server cluster switches the effective version of the service program according to the configuration of the shunting configuration server on the effective version of the service program of the server cluster, the server cluster may also send a version effectiveness message to the shunting configuration server, so that the shunting configuration server determines the effective version of the service program of the server cluster according to the version effectiveness message. The version validation message is used for indicating the current validation version of the service program of the server cluster.

It can be understood that, due to the hierarchical and regional caches of the DNS servers, after the traffic distribution configuration server synchronizes the traffic states of the plurality of server clusters to the DNS server, there may be a delay in traffic distribution of the DNS server to the plurality of server clusters, that is, the traffic of the plurality of server clusters may reach the traffic state synchronized by the traffic distribution configuration server after a period of delay. In this embodiment of the present application, the offloading configuration server may determine whether the traffic state synchronization of the server cluster is successful.

In an exemplary embodiment, the server cluster may feed back the monitored traffic allocated by the DNS server to the offloading configuration server, so that the offloading configuration server determines whether the traffic state synchronization of the server cluster is successful according to the monitored traffic. That is, after monitoring the traffic allocated by the DNS server in step 1201, the method may further include: and feeding back the flow to the flow distribution configuration server so that the flow distribution configuration server determines whether the flow state synchronization of the server cluster is successful according to the flow.

The method for upgrading the service program of the server cluster provided by the embodiment of the application monitors the flow distributed by the DNS to determine the state of the server cluster, upgrades the service program adopted by the server cluster from the first version to the second version under the condition that the state of the server cluster is the forbidden state, and feeds back a version upgrading message to the shunting configuration server, wherein the version upgrading message is used for indicating the server cluster to upgrade the service program from the first version to the second version. Therefore, the version upgrading of the service program of the server cluster is realized, and the condition that the data of the user end is disordered due to the mixed use of new and old versions when the version upgrading of the service program adopted by the server cluster is carried out is avoided.

Fig. 13 is a schematic structural diagram of a offloading configuration server according to an embodiment of the present application.

As shown in fig. 13, the offload configuration server 1300 may include: a monitoring module 1310, a configuration module 1320, and a synchronization module 1330.

The monitoring module 1310 is configured to monitor versions of service programs used by multiple server clusters;

a configuration module 1320, configured to configure traffic states of the multiple server clusters according to versions of service programs adopted by the multiple server clusters;

A synchronizing module 1330 configured to synchronize traffic states of the multiple server clusters to the DNS server, so that the DNS server performs traffic distribution on the multiple server clusters according to the updated traffic states.

Further, in a possible implementation manner of the embodiment of the present application, the configuring module 1320 includes:

the first configuration unit is used for configuring the plurality of server clusters to be in a first flow state under the condition that the version upgrading is required to be carried out on the service program of the target server cluster in the plurality of server clusters; the target server cluster is in a disabled state in the first traffic state, and the rest of the plurality of server clusters are in an enabled state;

the second configuration unit is used for configuring the plurality of server clusters to be switched from the first flow state to the second flow state when the service programs of the target server cluster in the forbidden state in the plurality of server clusters are upgraded from the first version to the second version and the effective version of the service programs is the first version; the target server cluster is in an enabled state under the second traffic state, and the rest server clusters are in a disabled state;

a third configuration unit, configured to, when the effective version of the service program in the target server cluster is switched from the first version to the second version, and the service programs in the remaining server clusters are upgraded from the first version to the second version, and the effective versions of the service programs in the remaining server clusters are the second version, configure the plurality of server clusters to be switched from the second flow state to the third flow state; and the target server cluster and the rest server clusters are in the starting state in the third flow state.

Further, in a possible implementation manner of the embodiment of the present application, the configuring module 1320 further includes:

the fourth configuration unit is used for configuring the effective version of the service program in the target server cluster as the first version;

and the first sending unit is used for sending the first version configuration message to the target server cluster so that the target server switches the effective version of the service program according to the first version configuration message.

a fifth configuration unit, configured to configure an effective version of the service program in the target server cluster as a second version;

and the second sending unit is used for sending a second version configuration message to the target server cluster so that the target server switches the effective version of the service program according to the second version configuration message.

a sixth configuration unit, configured to configure the effective version of the service program in the remaining server clusters as the second version;

and the third sending unit is used for sending the third version configuration message to the rest server clusters so as to enable the rest servers to switch the effective versions of the service programs according to the third version configuration message.

Further, in a possible implementation manner of the embodiment of the present application, the monitoring module 1310 includes:

the server cluster comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving a version upgrading message fed back by a plurality of server clusters, and the version upgrading message is used for indicating that the server clusters upgrade the service programs from a first version to a second version;

Further, in a possible implementation manner of the embodiment of the present application, the offloading configuration server may further include:

the acquisition module is used for respectively acquiring the monitored flow in the plurality of server clusters;

and the determining module is used for determining whether the traffic state synchronization of the plurality of server clusters is successful according to the traffic of each server cluster.

It should be noted that the explanation in the foregoing embodiment of the traffic configuration method of the server cluster executed by the offload configuration server side is also applicable to the offload configuration server in this embodiment, and details are not described here again.

According to the distribution configuration server, the flow states of the server clusters are configured according to the versions of the service programs adopted by the server clusters, the versions of the service programs providing services in the server clusters can be ensured to be consistent, and therefore the condition that data of a user terminal is disordered due to the mixed use of new and old versions when the versions of the service programs adopted by the server clusters are upgraded is avoided.

In order to implement the foregoing embodiment, an embodiment of the present application further provides a DNS server. Fig. 14 is a schematic structural diagram of a DNS server according to an embodiment of the present application.

As shown in fig. 14, the DNS server 1400 may include: a receiving module 1410 and an assigning module 1420.

The receiving module 1410 is configured to receive a traffic state synchronized by the traffic configuration server by using the traffic configuration method in the embodiment of the first aspect;

and an allocating module 1420, configured to allocate traffic to the multiple server clusters according to the traffic state.

It should be noted that the explanation in the embodiment of the traffic configuration method for a server cluster executed by the DNS server side is also applicable to the DNS server in this embodiment, and details are not described here.

The DNS server according to the embodiment of the present application receives the traffic state synchronized by the flow distribution configuration server using the traffic configuration method according to the embodiment of the first aspect, and performs traffic distribution on the plurality of server clusters according to the traffic state, thereby implementing traffic distribution on the plurality of server clusters according to the traffic state synchronized by the flow distribution configuration server.

In order to implement the foregoing embodiments, an embodiment of the present application further provides a server cluster. Fig. 15 is a schematic structural diagram of a server cluster provided in the embodiment of the present application.

As shown in fig. 15, the server cluster 1500 may include: monitoring module 1510, and upgrading module 1520.

The monitoring module 1510 is configured to monitor traffic allocated by the DNS server to determine a state of the server cluster; the traffic is obtained by the DNS server distributing traffic states synchronized by the traffic distribution configuration server according to the traffic configuration method of the embodiment of the first aspect;

and the upgrade module 1520 is configured to upgrade a version of the service program according to the state of the server cluster.

Further, in a possible implementation manner of the embodiment of the present application, the upgrade module 1520 includes:

and the upgrading unit is used for upgrading the service program adopted by the server cluster from the first version to the second version under the condition that the state of the server cluster is the forbidden state.

Further, in a possible implementation manner of the embodiment of the present application, the upgrade module 1520 further includes:

the server cluster comprises a first sending unit and a second sending unit, wherein the first sending unit is used for feeding back a version upgrading message to the shunting configuration server, and the version upgrading message is used for indicating that the server cluster upgrades the service program from the first version to the second version.

A receiving unit, configured to receive a version configuration message sent by a offload configuration server;

and the switching unit is used for switching the effective version of the service program according to the version configuration message.

Further, in a possible implementation manner of the embodiment of the present application, the upgrading module further includes:

and the second sending unit is used for sending the version validation message to the offloading configuration server, so that the offloading configuration server determines the validation version of the service program of the server cluster according to the version validation message.

Further, in a possible implementation manner of the embodiment of the present application, the server cluster 1500 may further include:

and the sending module is used for feeding back the flow to the flow distribution configuration server so that the flow distribution configuration server determines whether the flow state synchronization of the server cluster is successful or not according to the flow.

It should be noted that the explanation in the embodiment of the method for configuring traffic of a server cluster executed by the server cluster side is also applicable to the server cluster in this embodiment, and details are not described here again.

According to the server cluster, the state of the server cluster is determined by monitoring the flow distributed by the DNS, and the version of the service program is updated according to the state of the server cluster, so that the version of the service program of the server cluster is updated, and the condition that the data of a user end is disordered due to mixed use of new and old versions when the version of the service program adopted by the server cluster is updated is avoided.

In order to implement the foregoing embodiment, the present application further provides a traffic configuration system for a server cluster, which includes a plurality of server clusters, a offloading configuration server, and a DNS server.

The server cluster is used for executing the service program upgrading method of the embodiment;

the flow distribution configuration server is configured to execute the flow configuration method in the foregoing embodiment, so as to configure the flow states of the multiple server clusters;

the DNS server is configured to execute the traffic distribution method in the foregoing embodiment, so as to perform traffic distribution on multiple server clusters.

It should be noted that, the descriptions of the server cluster, the offloading configuration server and the DNS server in the foregoing embodiments are also applicable to the server cluster, the offloading configuration server and the DNS server in the traffic configuration system of the server cluster in the embodiment of the present application, and are not described here again.

Further, in a possible implementation manner of the embodiment of the present application, the traffic configuration system of the server cluster may further include a client. The client is used for accessing the client of the corresponding server cluster according to the flow distributed by the DNS server.

Further, after the service program in the server cluster is upgraded from the first version to the second version, in order to avoid that the upgraded version is unavailable, and thus the server cluster in which the version of the service program is upgraded cannot provide the service, in a possible implementation manner of the embodiment of the present application, the availability of the version of the service program in the server cluster may also be verified.

In a possible implementation manner of the embodiment of the present application, the client may verify, through the intranet, whether versions of service programs adopted by the multiple server clusters are available. That is, the client may also be used to: verifying that versions of service programs employed by a plurality of server clusters are available.

Specifically, for a server cluster in which the availability of the version of the service program needs to be verified, the to-be-verified version of the service program in the server cluster may be switched to an effective state, when a client accesses a specific website, an IP address of the server cluster corresponding to the website may be obtained through IP local mapping, and when the client may load specific content and services of the to-be-verified version from the server cluster, it may be determined that the to-be-verified version of the service program adopted by the server cluster is available.

It should be noted that the verification process of the version availability of the service program adopted by each server cluster is performed when each server cluster is in the disabled state.

The traffic configuration system for server clusters provided in the embodiments of the present application monitors versions of service programs used by a plurality of server clusters through a offload configuration server, configuring the traffic state of the plurality of server clusters according to the versions of the service programs adopted by the plurality of server clusters, and synchronizing the traffic status of the plurality of server clusters to the DNS server, the DNS server performs traffic configuration on the plurality of server clusters according to the traffic status synchronized by the shunting configuration server, each server cluster monitors the traffic distributed by the DNS server to determine the status of the server clusters, further, the version of the service program is upgraded according to the state of the server cluster, so that the versions of the service programs providing services in a plurality of server clusters can be ensured to be consistent, therefore, the condition that the data of the user terminal is disordered due to the mixed use of the new version and the old version when the version of the service program adopted by the server cluster is upgraded is avoided.

In order to implement the foregoing embodiment, the present application further provides an electronic device, including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can execute a traffic configuration method of a server cluster, a traffic distribution method of a server cluster, or a service program upgrade method of a server cluster, as set forth in any one of the foregoing embodiments of the present application.

In order to achieve the above embodiments, the present application further proposes a non-transitory computer readable storage medium storing computer instructions for causing a computer to execute a traffic configuration method of a server cluster, a traffic distribution method of a server cluster, or a service program upgrade method of a server cluster as proposed by any one of the foregoing embodiments of the present application.

In order to implement the foregoing embodiments, the present application further provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the computer program implements the traffic configuration method of the server cluster, the traffic distribution method of the server cluster, or the service program upgrade method of the server cluster, as provided in any one of the foregoing embodiments of the present application.

FIG. 16 illustrates a block diagram of an exemplary electronic device suitable for use in implementing embodiments of the present application. The electronic device 1600 shown in fig. 16 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application. The electronic device may be a offload configuration server, a DNS server, or a server cluster.

As shown in fig. 16, electronic device 1600 is in the form of a general purpose computing device. Components of electronic device 1600 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 that couples various system components including the system memory 28 and the processing unit 16.

Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, or a local bus using any of a variety of bus architectures. By way of example, such architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

Electronic device 1600 typically includes a variety of computer-system-readable media. Such media can be any available media that is accessible by electronic device 1600 and includes both volatile and nonvolatile media, removable and non-removable media.

Memory 28 may include computer system readable media in the form of volatile Memory, such as Random Access Memory (RAM) 30 and/or cache Memory 32. The electronic device 1600 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 16, commonly referred to as a "hard drive"). Although not shown in FIG. 16, a magnetic disk drive for reading from and writing to a removable nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable nonvolatile optical disk (e.g., a Compact disk Read Only Memory (CD-ROM), a Digital versatile disk Read Only Memory (DVD-ROM), or other optical media) may be provided. In these cases, each drive may be connected to bus 18 by one or more data media interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the application.

A program/utility 40 having a set (at least one) of program modules 42 may be stored, for example, in memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. Program modules 42 generally carry out the functions and/or methodologies of the embodiments described herein.

The electronic device 1600 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), one or more devices that enable a user to interact with the electronic device 1600, and/or any devices (e.g., network card, modem, etc.) that enable the electronic device 1600 to communicate with one or more other computing devices. Such communication may be through an input/output (I/O) interface 22. Moreover, the electronic device 1600 may also communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public Network such as the Internet via the Network adapter 20. As shown, the network adapter 20 communicates with the other modules of the electronic device 1600 via the bus 18. It should be appreciated that although not shown in FIG. 16, other hardware and/or software modules may be used in conjunction with electronic device 1600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

The processing unit 16 executes various functional applications and data processing, for example, implementing the methods mentioned in the foregoing embodiments, by running a program stored in the system memory 28.

In the description of the present specification, reference to the description of "one embodiment," "some embodiments," "an example," "a specific example," or "some examples" or the like means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Moreover, various embodiments or examples and features of various embodiments or examples described in this specification can be combined and combined by one skilled in the art without being mutually inconsistent.

Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or to implicitly indicate the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the feature. In the description of the present application, "plurality" means at least two, e.g., two, three, etc., unless explicitly specified otherwise.

Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing steps of a custom logic function or process, and alternate implementations are included within the scope of the preferred embodiment of the present application in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.

The logic and/or steps represented in the flowcharts or otherwise described herein, such as an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Further, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.

It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. If implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are well known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.

It will be understood by those skilled in the art that all or part of the steps carried out in the method of implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and the program, when executed, includes one or a combination of the steps of the method embodiments.

In addition, functional units in the embodiments of the present application may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a separate product, may also be stored in a computer-readable storage medium.

The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc. While embodiments of the present application have been shown and described above, it will be understood that the above embodiments are exemplary and should not be construed as limiting the present application and that changes, modifications, substitutions and alterations in the above embodiments may be made by those of ordinary skill in the art within the scope of the present application.

Claims

1. A traffic configuration method of a server cluster is applied to a shunting configuration server, and comprises the following steps:

monitoring versions of service programs adopted by a plurality of server clusters;

configuring the flow states of the plurality of server clusters according to the versions of the service programs adopted by the plurality of server clusters;

and synchronizing the traffic states of the plurality of server clusters to a Domain Name System (DNS) server so that the DNS server performs traffic distribution on the plurality of server clusters according to the updated traffic states.

2. The method of claim 1, wherein configuring the traffic states of the plurality of server clusters according to the versions of the service programs adopted by the plurality of server clusters comprises:

under the condition that a service program of a target server cluster in the plurality of server clusters needs to be subjected to version upgrading, configuring the plurality of server clusters to be in a first flow state; wherein the target server cluster is in a disabled state in the first traffic state, and the remaining server clusters in the plurality of server clusters are in an enabled state;

When a service program of a target server cluster in a disabled state in the plurality of server clusters is upgraded from a first version to a second version, and an effective version of the service program is the first version, configuring the plurality of server clusters to be switched from the first flow state to a second flow state; wherein the target server cluster is in an enabled state in the second traffic state, and the other server clusters are in a disabled state;

configuring the plurality of server clusters to switch from the second traffic state to a third traffic state when the effective versions of the service programs in the target server cluster are switched from the first version to the second version, and the service programs in the rest of server clusters are upgraded from the first version to the second version, and the effective versions of the service programs in the rest of server clusters are the second version; and in the third flow state, the target server cluster and the rest server clusters are in enabled states.

3. The method of claim 2, wherein prior to the configuring the plurality of server clusters to switch from the first traffic state to the second traffic state, further comprising:

Configuring the effective version of the service program in the target server cluster as the first version;

and sending a first version configuration message to the target server cluster so that the target server switches the effective version of the service program according to the first version configuration message.

4. The method of claim 2, further comprising, prior to the configuring the plurality of server clusters to switch from the second flow state to a third flow state:

configuring the effective version of the service program in the target server cluster as the second version;

5. The method of claim 2, further comprising, prior to the configuring the plurality of server clusters to switch from the second flow state to a third flow state:

configuring the effective version of the service program in the rest server clusters as the second version;

6. The method of claim 2, wherein the monitoring versions of service programs employed by the plurality of server clusters comprises:

receiving a version upgrading message fed back by a plurality of server clusters, wherein the version upgrading message is used for indicating that the server clusters upgrade the service programs from the first version to the second version;

and/or receiving a version validation message fed back by a plurality of server clusters, wherein the version validation message is used for indicating the validated versions of the service programs of the server clusters.

7. The method according to any of claims 1-6, further comprising, after said synchronizing traffic states of said plurality of server clusters to a Domain Name System (DNS) server:

respectively acquiring the monitored flow in the plurality of server clusters;

8. A traffic distribution method of a server cluster is applied to a DNS server, and comprises the following steps:

receiving a traffic state synchronized by a traffic configuration server by using the traffic configuration method according to any one of claims 1 to 7;

And carrying out flow distribution on the plurality of server clusters according to the flow state.

9. A service program upgrading method of a server cluster is applied to the server cluster and comprises the following steps:

monitoring traffic distributed by a DNS server to determine the state of the server cluster; the traffic is obtained by the DNS server distributing traffic states synchronized by the traffic distribution configuration server according to the traffic distribution configuration method according to any one of claims 1 to 7;

and upgrading the version of the service program according to the state of the server cluster.

10. The method of claim 9, wherein the performing a version upgrade of a service program according to the state of the server cluster comprises:

and upgrading the service program adopted by the server cluster from the first version to the second version under the condition that the state of the server cluster is the forbidden state.

11. The method of claim 10, wherein after upgrading the server program employed by the server cluster from the first version to the second version, further comprising:

feeding back a version upgrading message to a distribution configuration server, wherein the version upgrading message is used for indicating that the server cluster is upgraded from the first version to the second version.

12. The method of claim 10, wherein after upgrading the service program adopted by the server cluster from the first version to the second version, further comprising:

receiving a version configuration message sent by the shunting configuration server;

13. The method of claim 12, wherein after the switching the validated version of the service according to the version configuration message, further comprising:

and sending a version validation message to the distribution configuration server, so that the distribution configuration server determines the validation version of the service program of the server cluster according to the version validation message.

14. The method according to any one of claims 9-13, wherein after monitoring the traffic allocated by the DNS server, further comprising:

and feeding back the flow to the distribution configuration server so that the distribution configuration server determines whether the flow state synchronization of the server cluster is successful according to the flow.

15. A streaming configuration server, comprising:

the monitoring module is used for monitoring the versions of the service programs adopted by the plurality of server clusters;

The configuration module is used for configuring the flow states of the plurality of server clusters according to the versions of the service programs adopted by the plurality of server clusters;

and the synchronization module is used for synchronizing the traffic states of the plurality of server clusters to a Domain Name System (DNS) server so that the DNS server performs traffic distribution on the plurality of server clusters according to the updated traffic states.

16. A DNS server, comprising:

a receiving module, configured to receive a traffic state synchronized by the offload configuration server according to the traffic configuration method in any one of claims 1 to 7;

and the distribution module is used for carrying out flow distribution on the plurality of server clusters according to the flow state.

17. A cluster of servers, comprising:

the monitoring module is used for monitoring the flow distributed by the DNS server so as to determine the state of the server cluster; wherein, the traffic is obtained by the DNS server distributing according to the traffic state synchronized by the flow configuration server according to any one of claims 1 to 7 by using the traffic configuration method;

and the upgrading module is used for upgrading the version of the service program according to the state of the server cluster.

18. A traffic configuration system for a server cluster, comprising:

A plurality of server clusters for performing the service program upgrade method of any one of claims 9-14;

a traffic configuration server for performing the traffic configuration method of any of claims 1-7 to configure traffic states of a plurality of the server clusters; and

a DNS server for performing the traffic distribution method of claim 8 to distribute traffic to a plurality of the server clusters.

19. The flow configuration system of claim 18, further comprising:

and the client side is used for accessing the client side of the corresponding server cluster according to the flow distributed by the DNS server.

20. The traffic configuration system of claim 19, wherein the client is further configured to:

verifying that versions of service programs employed by a plurality of the server clusters are available.

21. An electronic device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-7, or the method of claim 8, or the method of any one of claims 9-14.

22. A non-transitory computer readable storage medium having stored thereon computer instructions for causing a computer to perform the method of any one of claims 1-7, or the method of claim 8, or the method of any one of claims 9-14.