A data processing method, device, storage medium and computer device

Abstract

Embodiments of the present application disclose a data processing method and device, a storage medium and a computer device. The version information and address information of nodes of a server cluster are acquired. The version information and address information are sent to an addressing cluster for registration. The server cluster is divided into at least two version login clusters based on the version information. The version information and account information of a client are acquired. The version login cluster of a target version is determined according to the version information of the client by the addressing cluster. The login identifier corresponding to the version login cluster of the target version is determined according to the account information of the client. The target node corresponding to the target address information of the login identifier is connected according to the target address information of the login identifier. In this way, the routing information of the server cluster of multiple versions is managed by the addressing cluster, the login identifier is generated to guide the connection between the client of different versions and the corresponding node, the system complexity is reduced, and the machine cost is reduced on the premise of load balancing.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, in particular to a data processing method and device, storage medium and computer equipment. BACKGROUND

[0002] In order to respond to the changes in the market and the needs of users, developers need to continuously modify and update Internet products, such as the release of new versions of application programs. In order to ensure smooth transition during the version release process, the blue-green release strategy is generally used. Blue-green release is a common deployment method without stopping service. The new version is deployed for testing without stopping the old version. After the new version runs stably, all traffic is switched to the new version. When the new version has problems, it can be quickly switched back to the old version. Therefore, during the blue-green release period, the backend cluster is in a state of coexistence of multiple versions.

[0003] During the blue-green distribution period, the updated client traffic needs to be guided into the corresponding backend cluster. In the prior art, a routing layer is added to maintain the node information of the backend cluster, so as to route to the corresponding backend cluster node according to the received version information and account information of the client. However, the introduction of the routing layer increases the message delay, and the traffic guiding behavior is introduced into the critical path of the entire message communication, increasing the machine cost and the complexity of system design. SUMMARY

[0004] The embodiments of the present application provide a data processing method and device, storage medium and computer equipment. The unnecessary time-consuming can be reduced, the machine cost and system complexity can be reduced, and the efficiency of establishing connection between the client and the corresponding node can be improved.

[0005] A data processing method comprises:

[0006] Obtaining version information and address information of nodes of a server cluster, wherein the server cluster comprises at least two versions of server clusters;

[0007] Sending the version information and the address information to an addressing cluster for registration, and dividing the server cluster into at least two versions of login clusters based on the version information;

[0008] Obtaining version information and account information of a client, and determining a target version of login cluster according to the version information of the client through the addressing cluster;

[0009] Determining a login identifier corresponding to the target version of login cluster according to the account information of the client, wherein the login identifier comprises target address information;

[0010] According to the target address information of the login identifier, the client and a target node corresponding to the target address information are connected.

[0011] Accordingly, the application provides a data processing apparatus, comprising:

[0012] An acquisition unit is configured to acquire version information and address information of nodes of a server cluster, wherein the server cluster comprises at least two versions of server clusters;

[0013] A sending unit is configured to send the version information and the address information to an addressing cluster for registration, and divide the server cluster into at least two versions of login clusters based on the version information;

[0014] A first determination unit is configured to acquire version information and account information of a client, and determine a target version of a login cluster according to the version information of the client through the addressing cluster;

[0015] A second determination unit is configured to determine a login identifier corresponding to the target version of the login cluster according to the account information of the client, wherein the login identifier comprises target address information;

[0016] A connection unit is configured to connect the client and a target node corresponding to the target address information according to the target address information of the login identifier.

[0017] In an embodiment, the data processing apparatus further comprises:

[0018] A prompting unit is configured to send update prompting information to the client, wherein the update prompting information guides the version information of the client to be updated from a current version to a first version.

[0019] In an embodiment, the data processing apparatus further comprises:

[0020] A first disconnection unit is configured to disconnect the connection between a client updated to the first version and a current node when the client updates the current version to the first version according to the update prompting information, wherein the current node is a node connected with the client of the current version;

[0021] A first receiving unit is configured to receive a reconnection request sent by the client updated to the first version.

[0022] In an embodiment, the data processing apparatus further comprises:

[0023] A first acquisition unit is configured to acquire the state of a client not updated to the first version.

[0024] a second disconnecting unit, configured to disconnect the client not updated to the first version from the current node when the client not updated to the first version is in an idle state;

[0025] a guiding unit, configured to send update prompt information to the client not updated to the first version, and guide the client not updated to the first version to update to the first version;

[0026] a second receiving unit, configured to receive a reconnection request sent by the client updated to the first version.

[0027] In an embodiment, the second determining unit comprises:

[0028] a first calculating sub-unit, configured to calculate a hash value of each node in the login cluster of the target version by using a consistent hashing algorithm, to obtain a first hash value, and map each node to a hash ring formed by the login cluster of the target version according to the first hash value;

[0029] a second calculating sub-unit, configured to calculate a hash value of the account information by using the consistent hashing algorithm, to obtain a second hash value, and map the account information to a first position in the hash ring according to the second hash value;

[0030] a searching sub-unit, configured to search along the hash ring clockwise from the first position, and determine the login identifier corresponding to the login cluster of the target version as an identifier corresponding to a searched node when the node is searched.

[0031] In an embodiment, the first calculating sub-unit is configured to:

[0032] calculate a hash value of each node in the login cluster of the target version by using the consistent hashing algorithm at least twice, to obtain at least two first hash values of each node and a corresponding virtual node;

[0033] map each virtual node to the hash ring formed by the login cluster of the target version according to the first hash value;

[0034] map the virtual node to a corresponding node.

[0035] In an embodiment, the first determining unit comprises:

[0036] a determining sub-unit, configured to determine, by using the addressing cluster, a login cluster of the target version which has the same version information as the client in the login cluster according to the version information of the client.

[0037] Further, the embodiment of the present application further provides a storage medium, which stores a plurality of instructions, and the instructions are suitable for being loaded by a processor to execute steps in any data processing method provided by the embodiment of the present application.

[0038] Further, the embodiment of the present application further provides a computer device, which comprises a processor and a memory, the memory stores an application program, and the processor is used to run the application program in the memory to implement the data processing method provided by the embodiment of the present application.

[0039] The sixth aspect of the embodiment of the present application provides a computer program product or a computer program, which comprises computer instructions stored in a storage medium. A processor of a computer device reads the computer instructions from the storage medium, and the processor executes the computer instructions, so that the computer device executes steps in the data processing method provided by the first aspect.

[0040] The embodiment of the present application obtains version information and address information of nodes of a server cluster; sends the version information and the address information to an addressing cluster for registration, divides the server cluster into at least two version login clusters based on the version information; obtains version information and account information of a client, and determines a target version login cluster of the client according to the version information of the client through the addressing cluster; determines a login identifier corresponding to the target version login cluster according to the account information of the client; and establishes a connection between the client and a target node corresponding to the target address information of the login identifier. In this way, the version information and the address information are sent to the addressing cluster for registration, the server cluster is divided into multiple version login clusters based on the version information, and then the routing information of the multiple version login clusters is managed through the addressing cluster, the login identifier is generated to guide different versions of the client to establish a connection with nodes of the corresponding server cluster, load balancing in multiple clusters is realized, the bypass design of the addressing cluster reduces the influence range of the addressing cluster failure, reduces the complexity of system disaster recovery design, and further reduces the machine deployment cost. BRIEF DESCRIPTION OF DRAWINGS

[0041] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed in the embodiment description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0042] Figure 1 is a data processing method implementation scene schematic diagram provided by the embodiment of the present application;

[0043] Figure 2This is a flowchart illustrating a data processing method provided in an embodiment of this application;

[0044] Figure 3 This is another schematic flowchart of a data processing method provided in an embodiment of this application;

[0045] Figure 4 This is a schematic diagram of the structure of a data processing method provided in an embodiment of this application;

[0046] Figure 5 This is a schematic diagram of a consistent hashing algorithm provided in an embodiment of this application;

[0047] Figure 6 This is a schematic diagram of the structure of the data processing apparatus provided in the embodiments of this application;

[0048] Figure 7 This is a schematic diagram of the structure of the computer device provided in the embodiments of this application. Detailed Implementation

[0049] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0050] This application provides a data processing method, apparatus, storage medium, and computer device. The data processing apparatus can be integrated into the computer device, which may be a server or a terminal, etc.

[0051] For better illustration of the embodiments of this application, please refer to the following terms:

[0052] Consistent hashing algorithm: Proposed by MIT in 1997, consistent hashing is a special hashing algorithm designed to solve the problem of distributed caching. When removing or adding a server, it minimizes changes to the existing mapping between service requests and the servers handling those requests. Consistent hashing solves the dynamic scaling problems that simple hashing algorithms encounter in distributed hash tables (DHTs).

[0053] Long-lived connection: refers to a connection that can continuously send multiple data packets. During the connection period, if no data packets are sent, both parties need to send link detection packets.

[0054] Routing: Routing refers to the process by which a router receives a packet on one interface, directs it based on the destination address, and forwards it to another interface.

[0055] Access layer: The access layer generally refers to the part of the network that directly faces user connections or access, and is a Socket Server daemon process that supports multiple connection methods. It supports long connection or short connection service through configuration. It also supports opening TCP or UDP protocol services through configuration.

[0056] Please refer to Figure 1 For example, the data processing device is integrated in a computer device, Figure 1 The implementation environment scenario diagram of the data processing method provided by the embodiment of the present application includes a server A and a terminal B. The server A can be a standalone physical server, a server cluster or a distributed system composed of multiple physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, network acceleration services (Content Delivery Network, CDN), and basic cloud computing services such as big data and artificial intelligence platforms. The server A can obtain version information and address information of nodes of a server cluster; send the version information and the address information to an addressing cluster for registration, divide the server cluster into at least two version login clusters based on the version information; obtain version information and account information of a client, and determine a target version login cluster of the client based on the version information of the client through the addressing cluster; determine a login identifier corresponding to the target version login cluster according to the account information of the client; and establish a connection between the client and a target node corresponding to the target address information of the login identifier.

[0057] The terminal B can be a smartphone, a tablet computer, a notebook computer, a desktop computer, or other computer devices that can install various applications required by users, but is not limited thereto. The server A and the terminal B can be directly or indirectly connected through wired or wireless communication, and the server A can receive data uploaded by the terminal B to perform corresponding data processing operations. The present application does not limit this.

[0058] It should be noted that Figure 1 The implementation environment scenario diagram of the data processing method shown is only an example, and the implementation environment scenario of the data processing method described in the embodiment of the present application is used to more clearly illustrate the technical solutions of the embodiment of the present application, and does not constitute a limitation on the technical solutions provided by the embodiment of the present application. Those skilled in the art can know that, with the evolution of data processing and the emergence of new business scenarios, the technical solutions provided by the present application are also applicable to similar technical problems.

[0059] The following will be described in detail respectively. It should be noted that the description order of the following embodiments is not limited as the preferred order of the embodiments.

[0060] This embodiment will be described from the perspective of a data processing apparatus, which can be integrated in a computer device, which can be a server or a terminal, and the present application does not limit here.

[0061] Please refer to Figure 2 , Figure 2 is a flowchart of a data processing method provided by the embodiment of the present application. The data processing method comprises:

[0062] In step 101, the version information and address information of the nodes of the server cluster are acquired.

[0063] With the rapid development of Internet technology, the market and user needs are constantly changing, and developers need to continuously modify and update Internet products, and then need to continuously upgrade the application program. Each upgrade can be identified by a version number, so that the application program is updated from the current version to the new version, so that each version of the application program corresponds to a version number (Version Number), wherein the version number is the identification number of the version. The version number enables the user to understand whether the application program used is the latest version and the functions and facilities it provides. The biggest challenge facing application program upgrade is the switching of new and old businesses, that is, bringing the software from the last stage of testing to the production environment, while ensuring uninterrupted system service. For a long time, business upgrades have gradually formed several release strategies: blue-green release, gray release and rolling release, the purpose is to avoid as much as possible the loss of traffic or service unavailability problems caused by release. Among them, in order to ensure smooth transition during the business upgrade release, that is, the user completes the release process without awareness, the blue-green release strategy is generally used. Blue-green release is a common deployment method without stopping service. The new version is deployed for testing without stopping the current version. After the new version runs stably, all traffic is switched to the new version. When the new version has problems, it can be quickly switched back to the original version. Therefore, during the blue-green release, the server cluster in the back end is in a state of multiple versions coexisting.

[0064] Therefore, after the client completes the update, the updated client in the new version needs to be guided to enter the new version of the server cluster to establish a connection with the new node, where the client can be a game client, and the updated game client in the new version enters the new version of the server cluster to establish a connection with the corresponding node, thereby logging into the corresponding version of the game lobby. At present, the mechanism commonly adopted is to realize traffic guidance in the form of a domain name system (DNS), that is, different versions of the client request the corresponding DNS to obtain the routing information such as the Internet Protocol (IP) address and port information of the corresponding backend server cluster node, and then establish a connection with the corresponding server cluster node through the obtained routing information.

[0065] However, the application scenarios of mobile games are often in weak network environments, and therefore, under the business characteristics of game business long connection, mobile game clients often face the situation of network switching and short-term disconnection caused by poor signals. Under this weak network background, when the network is disconnected and reconnected, the client needs to be connected and logged into the original connected node. Because the routing information of the association system often records the node logged in by the player before, if connected to a new node, the association system will trigger routing refreshing, which is complex and prone to problems. The routing information obtained through the DNS cannot guarantee the consistency of the nodes of the backend server cluster before and after the connection is disconnected, and is prone to routing jump problems after connection.

[0066] In order to solve the above routing jump problem, the prior art adds a routing jump layer behind the access layer component, each routing jump layer node maintains the node information of the backend server cluster, where the access layer component is a component for managing the connection between the client and the corresponding server node, which can be a cluster, and the access layer component can be a Tconnd access layer component. For each client connection request sent by the access layer component, the routing jump layer routes to the corresponding node of the backend server cluster according to the version information and account information of the request. However, the introduction of the routing jump layer will increase unnecessary message delay in the communication process between the client and the corresponding node of the server cluster, and the routing jump layer introduced for traffic guidance becomes the key path for communication between all clients and server nodes. When the routing jump layer fails, it will greatly affect the connection between the client and the node of the server cluster. Therefore, the complexity of system disaster recovery design is improved, and the cost of machine deployment is increased.

[0067] To solve the above problems, the embodiments of the present application introduce an addressing cluster with bypass design to manage the routing information of multiple versions of login clusters, so that the failure influence range of the addressing cluster is limited to the clients logged in during the failure, reducing the complexity of system disaster recovery design, and further reducing the cost of machine deployment, wherein the addressing cluster is composed of multiple routing servers (Route Server) providing addressing services, and the routing information of the server cluster is managed by registering the information of each node in the addressing cluster. For specific implementation process, please continue to refer to the following steps.

[0068] To manage the nodes of the server cluster in the back end, the version information and address information of each server node in the server cluster can be obtained after the node processes of different versions of server clusters are started, wherein the server cluster includes at least two versions of server clusters, for example, it can include a first version of server cluster built during blue-green release and a second version of server cluster providing services to the outside before blue-green release, the first version is a new version updated from the second version, in addition, when a problem occurs in the first version release process, the server cluster can also include a detection version of server cluster to verify the cause of the problem in the first version release process. The version information of the node of the server cluster is used to identify which version of the server cluster the node belongs to, and the address information of the node can include the IP address and port information of the server node.

[0069] In step 102, the version information and address information are sent to the addressing cluster for registration, and the server cluster is divided into at least two versions of login clusters based on the version information.

[0070] In order to facilitate the management and maintenance of each node of the addressing cluster, the version information and address information of each node can be sent to the addressing cluster composed of multiple routing servers providing addressing services. By registering the information of each node in the addressing cluster, the management of the routing information of the server cluster is realized. In order to avoid the centralized login of a version of client causing the uneven load of the nodes of the server cluster, the server cluster can be divided into different version login clusters according to the version information of the nodes by the addressing cluster. The login cluster corresponds to the server cluster and is a mapping of the server cluster set up in the addressing cluster to facilitate the addressing cluster to distribute the nodes of the server cluster according to the version information. For example, it is assumed that the server cluster in the back end includes a first version server cluster and a second version server cluster. Each version server cluster includes multiple server nodes of the corresponding version. When the addressing cluster receives a node with the version information of the first version, the node of this version can be summarized into the login cluster of this version. Thus, the first version login cluster and the second version login cluster can be obtained. Further, the first version login cluster corresponds to the first version server cluster, and the second version login cluster corresponds to the second version server cluster.

[0071] In step 103, the version information and account information of the client are obtained, and the target version login cluster is determined according to the version information of the client by the addressing cluster.

[0072] When the client requests to log in to the game hall, that is, requests to establish a connection with the node of the corresponding server cluster, the version information and account information need to be sent to the addressing cluster to obtain the corresponding login identifier, and then the connection with the corresponding node is established according to the login identifier. The login identifier includes address information, which is used to determine the node in the server cluster that establishes a connection with the client. Thus, the version information and account information sent by the client to the addressing cluster are obtained. According to the version information of the client, the same login cluster as the version information of the client is found in the divided login cluster by the addressing cluster, so as to determine the target version login cluster, that is, the corresponding version server cluster that establishes a connection with the client.

[0073] During the blue-green deployment, the update prompt information can be sent to the corresponding client to guide the user to update the version information of the client from the second version to the first version before the first version is released after the test is completed or during the open service time of the application product. According to specific conditions, the update prompt information can be sent to a part of the clients or to each client. In an embodiment, when the client updates the current version information from the second version to the first version according to the prompt of the update prompt information, the connection between the client updated to the first version and the current node is disconnected, and then a reconnection request sent by the client updated to the first version is received, so as to reacquire the version information and the account information of the client updated to the first version, and determine the target version login cluster according to the version information of the client, and then determine the target node to which the client is connected according to the account information, and connect with the target node, so as to complete the reconnection of the client updated to the first version. For the client that does not perform the operation of updating to the first version according to the guidance of the update prompt information, the current connection is maintained.

[0074] In an embodiment, when the technician prepares to recover the server cluster of the second version, it is necessary to perform a forced update operation on the client that is not updated to the first version according to the guidance of the update prompt information. At this time, the state of the client that is not updated to the first version is acquired, the connection between the client that is not updated to the first version and the current node is disconnected when the client that is not updated to the first version is in an idle state, which can be the state when the user switches the client to the background running, so as to send the update prompt information to the client that is not updated to the first version to guide the client that is not updated to the first version to update to the first version, and when the client that is not updated to the first version is updated to the first version, a reconnection request sent by the client updated to the first version is received, so as to reacquire the version information and the account information of the client updated to the first version, and determine the target node to which the client is connected based on the version information and the account information of the client, so as to complete the reconnection of the client updated to the first version.

[0075] In step 104, the login identifier corresponding to the login cluster of the target version is determined according to the account information of the client.

[0076] In order to determine the target node in the target version login cluster connected with the client, the login identifier corresponding to the target version login cluster can be determined according to the account information of the client, wherein the account information is a digital string or a character string allocated by the background system in order to identify each login client, and each account information uniquely identifies a client. The login identifier includes target address information, which is one-to-one corresponding to the target node. Therefore, the target node in the target version login cluster, that is, the server cluster, connected with the client can be determined through the login identifier.

[0077] In an embodiment, in order to reasonably allocate the load of each version of the server cluster node and realize the load balancing of each version of the server cluster node in the backend, the consistent hashing algorithm mechanism can be used. The hash value of each version of the login cluster node is calculated by using the hashing function through the addressing cluster, and then each node is mapped to the corresponding hash ring of the corresponding version of the login cluster according to the hash value. At the same time, the account information of the client requesting to obtain the login identifier is calculated by using the same hashing function to obtain the hash value of the account information of the client, and then the client is mapped to the corresponding hash ring of the corresponding version of the login cluster according to the hash value of the account information of the client. Thus, the client is searched along the hash ring in the clockwise direction, and when the first node is found, the identifier corresponding to the node is obtained, which is obtained based on the address information of the node. The identifier of the node is confirmed as the login identifier corresponding to the target version login cluster connected with the corresponding node.

[0078] In step 105, the target node corresponding to the target address information of the client and the target address information is connected.

[0079] The login identifier can be sent to the client, and then the login request sent by the client is received through the receiving layer component, the login identifier carried by the login request is obtained, and the target node corresponding to the target address information carried by the login identifier in the server cluster is connected according to the target address information, wherein the connection mode of the client and the server node can be a transmission control protocol (TCP) connection mode, so as to complete the connection of the client and the server node, and make the client successfully log in to the corresponding version of the game hall. Therefore, the data processing method provided in the embodiment of the application bypasses the routing information of the node of the addressing cluster management server cluster, guides the connection between the client of different versions and the target node of the server cluster of the corresponding version, thereby solving the problem of routing jump, reducing unnecessary time consumption, and reducing the load of the addressing cluster and the complexity of system disaster recovery design, thereby saving the cost of machine deployment.

[0080] As can be seen from the above, the version information and address information of the nodes of the server cluster are obtained; the version information and address information are sent to the addressing cluster for registration, the server cluster is divided into at least two version login clusters based on the version information; the version information and account information of the client are obtained, and the target version login cluster is determined according to the version information of the client through the addressing cluster; the login identifier corresponding to the target version login cluster is determined according to the account information of the client; and the target node corresponding to the target address information of the client and the target address information is connected according to the target address information of the login identifier. Therefore, the version information and address information are sent to the addressing cluster for registration, the server cluster is divided into multiple version login clusters based on the version information, and then the routing information of the multiple version login clusters is managed through the addressing cluster, the login identifier is generated to guide the connection between the client of different versions and the node of the corresponding server cluster, the load balancing in the multiple clusters is realized, the addressing cluster is bypassed, the influence range of the addressing cluster failure is reduced, the complexity of system disaster recovery design is reduced, and the machine deployment cost is reduced.

[0081] According to the method described in the above embodiment, the following examples will be further described in detail.

[0082] In this embodiment, the data processing device is integrated in a computer device. The data processing method takes the server as the execution subject, and takes the connection between the first version client and the corresponding node as an example for specific description.

[0083] As Figure 3As shown, Figure 3 Another flowchart of the data processing method provided by the embodiment is shown. The specific flow is as follows:

[0084] In step 201, the server obtains the version information and address information of the nodes of the server cluster, sends the version information and address information to the addressing cluster for registration, and divides the server cluster into at least two version login clusters based on the version information.

[0085] In order to manage the routing information of the nodes of the server cluster, the server can obtain the version information and address information of the nodes of the server cluster, and send the version information and address information of the nodes to the addressing cluster for registration. In order to avoid the problem of uneven load of the corresponding nodes caused by the centralized login of the clients of a certain version, the embodiment divides the nodes of the server cluster according to the version information of each node through the addressing cluster, thereby obtaining multiple version login clusters, so as to manage the load distribution of the nodes according to the version information, and realize the load balancing of the nodes of the multi-version server cluster. The login cluster is the mapping of the server cluster in the addressing cluster. For example, please refer to Figure 4 , Figure 4 The structural diagram of the data processing method provided by the embodiment is shown. It is assumed that the server cluster includes a first version server cluster 11 and a second version server cluster 12, each version server cluster includes multiple nodes with the same version information, the addressing cluster 13 divides the nodes with the first version information into the first version login cluster and the nodes with the second version information into the second version login cluster, thereby obtaining the first version login cluster and the second version login cluster, and then the corresponding load balancing distribution strategy can be performed on each version server cluster.

[0086] In step 202, the server sends an update prompt information to the client, disconnects the connection between the client updated to the first version and the current node when the client updates the current version to the first version according to the update prompt information, and receives the reconnection request sent by the client updated to the first version.

[0087] During the blue-green release, the update prompt information can be sent to the corresponding client to guide the user to update the version information of the client from the current second version to the first version before the release of the first version after the test is completed or during the open service time of the product. According to specific conditions, the update prompt information can be sent to a part of the clients or to all the clients. When the client updates the current version information from the current version to the first version according to the prompt of the update prompt information, the connection between the client updated to the first version and the current node is disconnected, and then a reconnection request sent by the client updated to the first version is received. The current node is a node connected with the client of the current version, so as to reacquire the version information and the account information of the client updated to the first version, determine the target version login cluster according to the version information of the client, and then determine the target node connected with the client according to the account information, and connect with the target node, so as to complete the reconnection of the client updated to the first version. In an embodiment, for the client which does not perform the operation of updating to the first version according to the guidance of the update prompt information, the connection between the client and the current node can be maintained.

[0088] In step 203, the server acquires the version information and the account information of the client, and determines the target version login cluster in the login cluster according to the version information of the client through the addressing cluster.

[0089] When the client requests to establish a connection with the node of the corresponding server cluster, the version information and the account information need to be sent to the addressing cluster to obtain the corresponding login identifier, and then the connection with the corresponding node is established according to the login identifier. Therefore, for the reconnection request sent by the client updated to the first version, the server acquires the version information and the account information of the client sent to the addressing cluster, and determines the target version login cluster in the login cluster according to the version information of the client through the addressing cluster, that is, determines the corresponding version server cluster to which the client establishes a connection. For example, please continue to refer to Figure 4 The server acquires the reconnection request sent by the client 14 updated to the first version, acquires the version information and the account information of the client 14 through the addressing cluster 13, and determines the login cluster with the version information of the first version in the login cluster according to the version information of the first version of the client 14, that is, determines the target version login cluster.

[0090] In step 204, the server performs at least two hash value calculations on each node in the target version login cluster by using the consistent hashing algorithm, to obtain at least two first hash values and corresponding virtual nodes of each node, and maps each virtual node to the hash ring composed of the target version login cluster according to the first hash value, and maps the virtual node to the corresponding node.

[0091] In order to avoid the problem of uneven node load caused by the centralized login of the account information corresponding to a number segment of the client, the virtual node mechanism of the consistent hashing algorithm can be used to manage each node. Specifically, at least two hash value calculations are performed on each node in the target version login cluster by using the consistent hashing algorithm, to obtain at least two hash values and at least two corresponding virtual nodes, and the corresponding virtual node is mapped to the hash ring composed of the target version login cluster according to the hash value, and the virtual node is mapped to the corresponding node.

[0092] Specifically, please refer to Figure 5 , Figure 5 is a schematic diagram of the consistent hashing algorithm. After the server obtains the version information and account information of the client updated to the first version, the target version login cluster is determined to be the first version login cluster according to the version information. It is assumed that the first version login cluster has two server nodes, node a and node b. Two hash value calculations are performed on the two nodes by using the same hash function according to the consistent hashing algorithm. The address information of the node can be selected as the key for the hash value calculation, to obtain two hash values and two corresponding virtual nodes of each node, which are virtual node a1, virtual node a2, virtual node b1 and virtual node b2. Each corresponding virtual node is mapped to the hash ring d composed of the first version login cluster according to the hash value, wherein virtual node a1 and virtual node a2 are mapped to node a, and virtual node b1 and virtual node b2 are mapped to node b. The hash ring d is a virtual circular ring formed by the consistent hashing algorithm on the entire hash space, wherein the value space of the hash function is 0 to 2 32 -1, that is, the hash value is a 32-bit integer number.

[0093] In step 205, the server performs a hash value calculation on the account information by using the consistent hashing algorithm, to obtain a second hash value, and maps the account information to the first position in the hash ring according to the second hash value.

[0094] In order to determine the target node connected to the client updated to the first version, please continue to refer to Figure 5The server calculates the hash value of the account information c of the client according to the same hash function in step 204 through a consistent hash algorithm, obtains a second hash value, and maps the account information c to the first position of the hash ring d corresponding to the login cluster of the first version according to the second hash value.

[0095] In step 206, the server starts searching along the hash ring clockwise from the first position, and when a node is found, the identifier corresponding to the found node is determined as the login identifier corresponding to the login cluster of the target version.

[0096] Please continue to refer to Figure 5 According to the consistent hash algorithm, the server starts searching along the hash ring d clockwise from the first position, and when a node is found, that is, the virtual node a1 is found, the found virtual node a1 is mapped to the node a, and the identifier corresponding to the node a is determined as the login identifier corresponding to the login cluster of the target version, that is, the login identifier corresponding to the login cluster of the first version. The login identifier includes target address information, that is, the address information of the node a. In this way, the consistent hash algorithm in the form of a virtual node is used to allocate the load of the nodes of each version of the server cluster, which solves the problem of uneven load of the nodes caused by the concentrated login of the clients in some number segments, and realizes the load balancing of the nodes of each version of the server cluster. In an embodiment, the login identifier can be sent to the client, and the client sends the login identifier to the access layer component to connect to the corresponding node.

[0097] In step 207, the server establishes a connection between the client and the target node corresponding to the target address information according to the target address information of the login identifier.

[0098] Please continue to refer to Figure 4 The server can obtain the login identifier sent by the client 14 through the access layer component 105, establish a connection between the client 14 and the target node in the first version of the server cluster 11 according to the target address information of the login identifier, and the connection between the client and the target node can be in the form of TCP connection.

[0099] In an embodiment, when the technician prepares to recycle the second version of the server cluster, it is necessary to perform a forced update operation on the client that has not updated the version information to the first version according to the guidance of the update prompt information. At this time, the step of performing a forced update on the client that has not updated the version information to the first version according to the guidance of the update prompt information can include:

[0100] (1) Obtain the state of the client that has not been updated to the first version;

[0101] (2) disconnecting the connection between the client not updated to the first version and the current node when the client not updated to the first version is in an idle state;

[0102] (3) sending an update prompt to the client not updated to the first version to guide the client not updated to the first version to update to the first version;

[0103] (4) receiving a reconnection request sent by the client updated to the first version.

[0104] When the client not updated to the first version logs in, that is, establishes a connection with the current node, the state of the client not updated to the first version is acquired, the connection between the client not updated to the first version and the current node is disconnected when the client not updated to the first version is in an idle state, the idle state can be a state when the user switches the client to background running, and then an update prompt is sent to the client not updated to the first version to guide the client not updated to the first version to update to the first version, when the client not updated to the first version is updated to the first version, a reconnection request sent by the client updated to the first version can be received without user awareness, thereby reacquiring version information and account information of the client updated to the first version through the addressing cluster, determining a login cluster of a target version according to the version information of the client, determining a login identifier corresponding to the node establishing a connection with the client in the login cluster of the target version according to the account information of the client through a consistent hashing algorithm, and realizing the connection between the client and a target node in the server cluster through an access layer component according to target address information carried by the login identifier, so as to complete the reconnection of the client updated to the first version.

[0105] From the above, the embodiment of the application obtains the version information and address information of the nodes of the server cluster through the server, sends the version information and address information to the addressing cluster for registration, divides the server cluster into at least two version login clusters based on the version information, sends the update prompt information to the client by the server, disconnects the connection between the client updated to the first version and the current node when the client updates the current version to the first version according to the update prompt information, receives the reconnection request sent by the client updated to the first version, obtains the version information and account information of the client, and determines the target version login cluster in the login cluster with the same version information as the client through the addressing cluster according to the version information of the client, calculates the hash value of each node in the target version login cluster at least twice through the consistent hash algorithm, obtains at least two first hash values of each node and the corresponding virtual node, maps each virtual node to the hash ring composed of the target version login cluster according to the first hash value, and maps the virtual node to the corresponding node. The server calculates the hash value of the account information through the consistent hash algorithm, obtains a second hash value, and maps the account information to a first position in the hash ring according to the second hash value. The server starts clockwise searching along the hash ring from the first position, determines the login identifier corresponding to the target version login cluster as the identifier corresponding to the target node of the target address information when the node is found, and establishes a connection between the client and the target node corresponding to the target address information according to the target address information of the login identifier. In this way, the version information and address information are sent to the addressing cluster for registration, the server cluster is divided into multiple version login clusters based on the version information, and then the routing information of the multiple version login clusters is managed and maintained through the addressing cluster using the consistent hash algorithm based on the virtual node form, and the login identifier is generated to guide the connection between the clients of different versions and the nodes of the corresponding server cluster, thereby avoiding the problem of uneven load of the server cluster caused by the centralized login of the clients corresponding to the account information of a certain number segment, thereby realizing the load balancing of the multiple clusters, and the bypass design of the addressing cluster reduces the influence range of the addressing cluster failure, reduces the complexity of the system disaster recovery design, and further reduces the machine deployment cost.

[0106] In order to better implement the above method, the embodiment of the application further provides a data processing apparatus, which can be integrated in a network device, such as a server or a terminal device, etc. The terminal device can include a tablet computer, a notebook computer, and / or a personal computer, etc.

[0107] For example, as shown in Figure 6 The data processing apparatus can include an obtaining unit 301, a sending unit 302, a first determining unit 303, a second determining unit 304, and a connecting unit 305, as follows:

[0108] The acquisition unit 301 is configured to acquire version information and address information of nodes of a server cluster, the server cluster including at least two versions of server clusters;

[0109] The sending unit 302 is configured to send the version information and the address information to an addressing cluster for registration, and divide the server cluster into at least two versions of login clusters based on the version information;

[0110] The first determination unit 303 is configured to acquire version information and account information of a client, and determine a target version of login cluster according to the version information of the client through the addressing cluster;

[0111] The second determination unit 304 is configured to determine a login identifier corresponding to the target version of login cluster according to the account information of the client, the login identifier including target address information;

[0112] The connection unit 305 is configured to establish a connection between the client and a target node corresponding to the target address information according to the target address information of the login identifier.

[0113] In an embodiment, the data processing apparatus further includes:

[0114] The prompting unit is configured to send update prompt information to the client, the update prompt information guiding the version information of the client to be updated from a current version to a first version.

[0115] In an embodiment, the data processing apparatus further includes:

[0116] The first disconnection unit is configured to disconnect the connection between the client updated to the first version and a current node when the client is updated to the first version according to the update prompt information, the current node being a node connected with the client of the current version;

[0117] The first receiving unit is configured to receive a reconnection request sent by the client updated to the first version.

[0118] In an embodiment, the data processing apparatus further includes:

[0119] The first acquisition unit is configured to acquire a state of a client not updated to the first version;

[0120] The second disconnection unit is configured to disconnect the connection between the client not updated to the first version and a current node when the client not updated to the first version is in an idle state;

[0121] The guiding unit is configured to send update prompt information to the client not updated to the first version, and guide the client not updated to the first version to be updated to the first version;

[0122] The second receiving unit is configured to receive a reconnection request sent by the client updated to the first version.

[0123] In an embodiment, the second determining unit comprises:

[0124] The first calculating sub-unit is configured to calculate a hash value of each node in the target version of the login cluster by using a consistent hashing algorithm, to obtain a first hash value, and map each node to a hash ring formed by the target version of the login cluster according to the first hash value.

[0125] The second calculating sub-unit is configured to calculate a hash value of the account information by using a consistent hashing algorithm, to obtain a second hash value, and map the account information to a first position in the hash ring according to the second hash value.

[0126] The searching sub-unit is configured to search along the hash ring clockwise from the first position, and determine the login identifier corresponding to the target version of the login cluster as the login identifier corresponding to the searched node when the node is searched.

[0127] In an embodiment, the first calculating sub-unit is configured to:

[0128] Calculate a hash value of each node in the target version of the login cluster by using a consistent hashing algorithm at least twice, to obtain at least two first hash values of each node and a corresponding virtual node.

[0129] Map each virtual node to the hash ring formed by the target version of the login cluster according to the first hash value.

[0130] Map the virtual node to the corresponding node.

[0131] In an embodiment, the first determining unit comprises:

[0132] The determining sub-unit is configured to determine the target version of the login cluster in the login cluster which is the same as the version information of the client according to the version information of the client by using the addressing cluster.

[0133] In implementation, each of the above units can be implemented as an independent entity, or can be combined as the same or several entities, and the specific implementation of each of the above units can refer to the method embodiments above, which will not be described here.

[0134] From the above, the embodiment of the application obtains the version information and address information of the nodes of the server cluster through the obtaining unit 301; the sending unit 302 sends the version information and address information to the addressing cluster for registration, divides the server cluster into at least two version login clusters based on the version information; the first determining unit 303 obtains the version information and account information of the client, and determines the target version login cluster according to the version information of the client through the addressing cluster; the second determining unit 304 determines the login identifier corresponding to the target version login cluster according to the account information of the client; the connecting unit 305 establishes a connection between the client and the target node corresponding to the target address information of the login identifier according to the target address information. In this way, the version information and address information are sent to the addressing cluster for registration, the server cluster is divided into multiple version login clusters based on the version information, and then the routing information of the multiple version login clusters is managed through the addressing cluster, the login identifier is generated to guide different versions of the client to establish a connection with the nodes of the corresponding server cluster, the load balancing in the multiple clusters is realized, the bypass design of the addressing cluster reduces the influence range of the addressing cluster failure, reduces the complexity of the system disaster recovery design, and further reduces the machine cost.

[0135] The embodiment of the application also provides a computer device, as shown in the figure, which shows a structural schematic diagram of the computer device related to the embodiment of the application, in particular: Figure 7

[0136] The computer device can include a processor 401 with one or more processing cores, a memory 402 with one or more computer readable storage media, a power supply 403, and an input unit 404, and the like. Those skilled in the art can understand that the computer device structure shown in the figure does not constitute a limitation on the computer device, and can include more or fewer components than the figure, or combine certain components, or different component arrangements. Among them: Figure 7

[0137] The processor 401 is the control center of the computer device, connects all parts of the computer device through various interfaces and lines, executes the software programs and / or modules stored in the memory 402 and the data stored in the memory 402, processes the data of the computer device, and thus detects the computer device as a whole. Optionally, the processor 401 can include one or more processing cores; preferably, the processor 401 can integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface and application program, etc., and the modem processor mainly processes wireless communication. It can be understood that the above-mentioned modem processor can also not be integrated into the processor 401.

[0138] ​​The memory 402 can be used to store software programs and modules, and the processor 401 executes various function applications and data processing by running the software programs and modules stored in the memory 402. The memory 402 can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, application programs required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; and the data storage area can store data created according to the use of the computer device, etc. In addition, the memory 402 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state memory device. Accordingly, the memory 402 can also include a memory controller to provide the processor 401 with access to the memory 402.

[0139] The computer device further includes a power supply 403 for powering the various components. Preferably, the power supply 403 can be logically connected to the processor 401 through a power management system, so as to realize functions such as management of charging, discharging, and power consumption management through the power management system. The power supply 403 can also include one or more direct current or alternating current power supplies, a recharging system, a power supply fault detection circuit, a power supply converter or inverter, a power supply state indicator, and the like.

[0140] The computer device can further include an input unit 404, which can be used to receive input digital or character information, and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function controls.

[0141] Although not shown, the computer device can also include a display unit and the like, which will not be described here. Specifically, in the present embodiment, the processor 401 in the computer device loads one or more executable files corresponding to the processes of the application programs into the memory 402 according to the following instructions, and runs the application programs stored in the memory 402 by the processor 401, so as to realize various functions, as follows:

[0142] Obtain version information and address information of nodes of a server cluster; send the version information and the address information to an addressing cluster for registration, divide the server cluster into at least two version login clusters based on the version information; obtain version information and account information of a client, and determine a target version login cluster of the client according to the version information of the client through the addressing cluster; determine a login identifier corresponding to the target version login cluster according to the account information of the client; and establish a connection between the client and a target node corresponding to the target address information of the login identifier according to the target address information of the login identifier.

[0143] The specific implementation of the above operations can refer to the foregoing embodiments, which will not be described herein again. It should be noted that the computer device provided in the embodiments of the present application and the data processing method in the foregoing embodiments belong to the same concept, and the specific implementation process is described in the foregoing method embodiments, which will not be described herein again.

[0144] Those skilled in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructions, or by related hardware controlled by the instructions, which can be stored in a computer readable storage medium and loaded and executed by a processor.

[0145] Therefore, the embodiments of the present application provide a storage medium, which stores a plurality of instructions. The instructions can be loaded by a processor to execute the steps in any data processing method provided by the embodiments of the present application. For example, the instructions can execute the following steps:

[0146] Obtain version information and address information of nodes of a server cluster; send the version information and the address information to an addressing cluster for registration, and divide the server cluster into at least two version login clusters based on the version information; obtain version information and account information of a client, and determine a target version login cluster of the client according to the version information of the client through the addressing cluster; determine a login identifier corresponding to the target version login cluster according to the account information of the client; and establish a connection between the client and a target node corresponding to the target address information of the login identifier.

[0147] The specific implementation of the above operations can refer to the foregoing embodiments, which will not be described herein again.

[0148] The storage medium can include a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0149] Since the instructions stored in the storage medium can execute the steps in any data processing method provided by the embodiments of the present application, the beneficial effects of any data processing method provided by the embodiments of the present application can be achieved, which are described in detail in the foregoing embodiments, which will not be described herein again.

[0150] According to an aspect of the present application, a computer program product or a computer program is provided, which includes computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method provided in any of the various optional implementation manners provided in the foregoing embodiments.

[0151] The above describes in detail a data processing method, device, storage medium and computer device provided by an embodiment of the application. The principles and implementation manners of the application are described by applying specific examples. The above description of the embodiments is only used to help understand the method of the application and its core idea. Meanwhile, for those skilled in the art, the specific implementation manners and application ranges will be changed according to the idea of the application. In conclusion, the content of the specification should not be understood as a limitation of the application.

Claims

1. A data processing method, characterized by, The application relates to a method for managing a server cluster, comprising the following steps: acquiring version information and address information of nodes of a server cluster, the server cluster comprising at least two versions of server clusters; sending the version information and the address information to a routing cluster for registration, and dividing the server cluster into at least two versions of login clusters based on the version information; wherein the routing cluster is composed of multiple routing servers providing routing services, and the routing information of the server cluster is managed by registering the information of each node in the routing cluster; acquiring version information and account information of a client, and determining a target version of a login cluster of the client according to the version information of the client through the routing cluster; determining a login identifier corresponding to the target version of the login cluster according to the account information of the client, the login identifier comprising target address information; establishing a connection between the client and a target node corresponding to the target address information according to the target address information of the login identifier.

2. The data processing method of claim 1, wherein, Before the step of acquiring version information and account information of a client, and determining a target version of a login cluster of the client according to the version information of the client through the routing cluster, the following step is further included: sending an update prompt to the client, the update prompt guiding the version information of the client to be updated from a current version to a first version.

3. The data processing method of claim 2, wherein, After the step of sending an update prompt to the client, the following steps are further included: when the current version of the client is updated to the first version according to the update prompt, disconnecting the connection between the client updated to the first version and a current node, the current node being a node connected with the client of the current version; receiving a reconnection request sent by the client updated to the first version.

4. The data processing method of claim 2, wherein, After the step of sending an update prompt to the client, the following steps are further included: acquiring the state of a client not updated to the first version; when the client not updated to the first version is in an idle state, disconnecting the connection between the client not updated to the first version and a current node; sending an update prompt to the client not updated to the first version, guiding the client not updated to the first version to be updated to the first version; receiving a reconnection request sent by the client updated to the first version.

5. The data processing method of claim 1, wherein, The step of determining a login identifier corresponding to the target version of the login cluster according to the account information of the client comprises the following steps: calculating the hash value of each node in the target version of the login cluster through a consistent hash algorithm to obtain a first hash value, and mapping each node to a hash ring composed of the target version of the login cluster according to the first hash value; calculating the hash value of the account information through a consistent hash algorithm to obtain a second hash value, and mapping the account information to a first position in the hash ring according to the second hash value; starting from the first position and searching along the hash ring clockwise, and determining the identifier of the found node as the login identifier corresponding to the target version of the login cluster.

6. The data processing method of claim 5, wherein, The first hash value is obtained by calculating the hash value of each node in the target version login cluster by using the consistent hash algorithm, and each node is mapped to a hash ring composed of the target version login cluster according to the first hash value, including: At least two hash values of each node in the target version login cluster are calculated by using the consistent hash algorithm to obtain at least two hash values of each node and corresponding virtual nodes; Each virtual node is mapped to a hash ring composed of the target version login cluster according to the first hash value; The virtual node is mapped to the corresponding node.

7. The data processing method of claim 1, wherein, The target version login cluster is determined according to the version information of the client by using the addressing cluster, including: The target version login cluster in the login cluster that is the same as the version information of the client is determined according to the version information of the client by using the addressing cluster.

8. A data processing apparatus, characterized by, Including: An acquisition unit is configured to acquire version information and address information of nodes of a server cluster, the server cluster including at least two versions of server clusters; A sending unit is configured to send the version information and the address information to an addressing cluster for registration, and divide the server cluster into at least two versions of login clusters based on the version information; wherein the addressing cluster is composed of a plurality of routing servers providing addressing services, and the routing information of the server cluster is managed by registering the information of each node in the addressing cluster; A first determination unit is configured to acquire version information and account information of a client, and determine a target version login cluster according to the version information of the client by using the addressing cluster; A second determination unit is configured to determine a login identifier corresponding to the target version login cluster according to the account information of the client, the login identifier including target address information; A connection unit is configured to establish a connection between the client and a target node corresponding to the target address information according to the target address information of the login identifier.

9. The data processing apparatus of claim 8, wherein, The data processing device further includes: A prompt unit is configured to send update prompt information to the client, the update prompt information guiding the version information of the client to be updated from a current version to a first version.

10. The data processing apparatus of claim 9, wherein, The data processing device further includes: A first disconnection unit is configured to disconnect the connection between the client updated to the first version and a current node when the client updates the current version to the first version according to the update prompt information, the current node being a node connected with the client of the current version; A first receiving unit is configured to receive a reconnection request sent by the client updated to the first version.

11. The data processing apparatus of claim 9, wherein, The data processing device further includes: A first acquisition unit is configured to acquire the state of a client that is not updated to the first version; A second disconnection unit is configured to disconnect the connection between the client that is not updated to the first version and a current node when the client that is not updated to the first version is in an idle state; A guiding unit is configured to send update prompt information to the client that is not updated to the first version, and guide the client that is not updated to the first version to update to the first version; The second receiving unit is configured to receive a reconnection request sent by the client updated to the first version.

12. The data processing apparatus of claim 8, wherein, The second determining unit comprises: The first computing sub-unit is configured to calculate a hash value of each node in the target version of the login cluster by using a consistent hashing algorithm to obtain a first hash value, and map each node to a hash ring composed of the target version of the login cluster according to the first hash value. The second computing sub-unit is configured to calculate a hash value of the account information by using the consistent hashing algorithm to obtain a second hash value, and map the account information to a first position in the hash ring according to the second hash value. The finding sub-unit is configured to find along the hash ring clockwise from the first position, and determine an identifier corresponding to a found node as a login identifier corresponding to the target version of the login cluster when the node is found.

13. The data processing apparatus of claim 12, wherein, The first computing sub-unit is configured to calculate a hash value of each node in the target version of the login cluster at least twice by using the consistent hashing algorithm to obtain at least two first hash values of each node and corresponding virtual nodes. Each virtual node is mapped to the hash ring composed of the target version of the login cluster according to the first hash value, and the virtual node is mapped to the corresponding node.

14. The data processing apparatus of claim 8, wherein, The first determining unit comprises: The determining sub-unit is configured to determine, by using the addressing cluster, a target version of the login cluster in the login cluster that is the same as version information of the client according to the version information of the client.

15. A storage medium, characterized by The storage medium stores a plurality of instructions, and the instructions are adapted to be loaded by the processor to execute the steps in the data processing method of any one of claims 1 to 7.

16. A computer device, comprising: The computer device comprises a memory and a processor; the memory stores an application program, and the processor is used to run the application program in the memory to execute the steps in the data processing method of any one of claims 1 to 7.

17. A computer program product, characterised in that, The computer program product comprises computer instructions stored in a storage medium; a processor of a computer device reads the computer instructions from the storage medium, and the processor executes the computer instructions to enable the computer device to execute the steps in the data processing method of any one of claims 1 to 7.

Images