CN106549875B - A session management method, device and load balancer - Google Patents

Abstract

The present invention provides a session management method, device, and load balancer. The session management method includes: receiving user request information; retrieving the corresponding first website server address in the session routing table according to the user request information; In the case of a website server address, obtain a second website server address according to the load balancing strategy, and route the user request information to the corresponding second website server according to the second website server address, and record the corresponding first routing information in the session routing table , the corresponding first routing information is sent to other load balancers in the load balancing cluster for synchronous update. The scheme provided by the present invention realizes the user's session request and session maintenance function; at the same time, it ensures that when the same user uses it again, its request can be accurately forwarded to the website server with its session information, providing users with better Interactive experience.

Description

A session management method, device and load balancer

technical field

The invention relates to the technical field of mobile communication, in particular to a session management method, device and load balancer.

Background technique

Load Balancer (LoadBalance), as an indispensable cluster network load balancing device in the current mainstream system architecture, has been deployed in the company's major information systems and has become an important part of the information system. When the load balancer is abnormally unavailable, the system will not be able to receive and process user requests, resulting in the failure of normal access to the system. How to ensure the high availability of the load balancer has become an important issue that must be considered when designing the system architecture.

Among them, the load balancer is also often referred to as "four to seven layers of switches", which respectively support four layers of network switching protocols and seven layers of network switching protocols. The functions of each layer of the protocol are shown in Figure 1. The seven-layer load balancing is introduced in detail:

Four-layer load balancing: that is, the final selected WEB server is determined mainly through the destination address and port in the message, plus the website WEB server selection strategy set by the load balancing device.

As shown in Figure 2, taking the common three-way handshake TCP as an example, when the load balancing device receives the first handshake signal SYN request from the client, it selects an optimal web server through the above method, and The target IP address is modified (changed to the back-end WEB server IP) and forwarded directly to the WEB server. The establishment of a TCP connection, that is, the three-way handshake is directly established between the client and the WEB server, and the load balancing device only performs a forwarding action similar to a router. In some deployment situations, in order to ensure that the return packet from the web server can be correctly returned to the load balancing device, the original source address of the packet may be modified while forwarding the packet.

Seven-layer load balancing: also known as "content switching", that is, mainly through the really meaningful application layer content in the message, plus the WEB server selection strategy set by the load balancing device, the final selected WEB server is determined.

As shown in Figure 3, taking the common TCP as an example, if the load balancing device wants to select a WEB server based on the real application layer content, it can only be possible after establishing a connection between the final WEB server and the client (three-way handshake). After receiving the message of the real application layer content sent by the client, and then according to the specific fields in the message and the WEB server selection policy set by the load balancing device, the final selected WEB server is determined. A load balancing device is more like a proxy server in this case. The load balancer and the front-end client and the back-end WEB server will establish TCP connections respectively.

In order to ensure high availability of the load balancer, a load balancing architecture deployed in an active-standby (HA) mode appears in the prior art. This architecture adopts load balancing devices that support the seven-layer network switching protocol. One primary load balancing device provides external services, and the other standby load balancing device is in a standby state and does not provide external services, as shown in Figure 4. In this way, when the primary load balancing device fails, it can be manually or automatically switched to the standby load balancing device to continue to provide external services.

With the centralized construction of the company's information system, a large number of users request concurrent access to the information system. In order to expand the system throughput, the mainstream architecture adopts the model of front-end load balancing equipment and back-end WEB server cluster, and as the core load balancing equipment responsible for request distribution Most of them are deployed in active/standby mode, and they work at a single point for a long time (only one load balancing device provides external services), without the support of cluster mode, the pressure of concurrent access is high, and the high availability capability is poor, which easily affects the normal access of information systems , running slowly and crashing; in addition, when the primary device fails over to the standby device, the information system will be temporarily inaccessible during the switchover process, and user session information will be lost, resulting in poor user experience.

On the other hand, with the development and maturity of LVS (Linux Virtual Server, a virtual server cluster system) technology, a load-balancing cluster architecture based on LVS technology and supporting four-layer network switching protocols has emerged. , the architecture can distribute the load to each load balancing device in the cluster according to its load balancing strategy, and dynamically adjust the number of members of the load balancing cluster according to the needs of the business, which has good scalability and high availability characteristics.

However, because the LVS load balancing cluster architecture only supports four-layer network protocols, it cannot analyze and process user request data, so that the load balancing architecture cannot guarantee that each request of the user is forwarded to the WEB server instance that stores the user session information In practice, the user session information is lost, and the normal processing of the request cannot be guaranteed, so it is not widely used in the actual production system.

Contents of the invention

The purpose of the present invention is to provide a session management method, device and load balancer, which solves the problem in the prior art that the load balancing method easily causes loss of user session information and affects user experience.

In order to solve the above technical problems, an embodiment of the present invention provides a session management method, which is applied to any load balancer in the load balancing cluster, including:

Receive user request information;

Retrieving the corresponding first website server address in the session routing table according to the user request information;

When the first website server address is not retrieved, obtain a second website server address according to the load balancing strategy, and route the user request information to the corresponding second website server according to the second website server address, and The corresponding first routing information is recorded in the session routing table, and the corresponding first routing information is sent to other load balancers in the load balancing cluster for synchronous update.

Optionally, the session management method also includes:

When the first website server address is detected, the user request information is routed to a corresponding first website server according to the first website server address.

Optionally, the step of receiving user request information specifically includes:

Receive user request information routed by the network management system according to the open shortest path first OSPF network protocol.

Optionally, the session management method also includes:

Regularly check whether the web server in the web server cluster corresponding to the load balancing cluster is available;

When it is unavailable, replace the second routing information corresponding to the unavailable website server with the third routing information corresponding to the standby website server in the session routing table, and send the replacement information to the load The other load balancers in the balancing cluster are updated synchronously.

Optionally, when it is unavailable, the step of replacing the second routing information corresponding to the unavailable website server with the third routing information corresponding to the standby website server in the session routing table includes:

When unavailable, generate exception report information;

The unavailable second routing information corresponding to the website server is replaced in the session routing table with third routing information corresponding to the backup website server according to the abnormality report information.

Optionally, the session management method also includes:

When receiving fourth routing information or update information sent by other load balancers in the load balancing cluster, the local session routing table is synchronously updated.

Optionally, when receiving fourth routing information or update information sent by other load balancers in the load balancing cluster, the step of synchronously updating the local session routing table includes:

When receiving fourth routing information sent by other load balancers in the load balancing cluster, adding the fourth routing information to the local session routing table;

When receiving the update information sent by other load balancers in the load balancing cluster, look up the fifth routing information of the corresponding unavailable website server in the local session routing table according to the update information, and transfer the fifth routing information of the corresponding unavailable website server. The fifth routing information is modified to the sixth routing information of the standby website server corresponding to the unavailable website server in the update information.

The present invention also provides a session management device, which is applied to any load balancer in the load balancing cluster, including:

A receiving module, configured to receive user request information;

A retrieval module, configured to retrieve the corresponding first website server address in the session routing table according to the user request information;

The first processing module is configured to obtain a second website server address according to a load balancing strategy when the first website server address is not retrieved, and route the user request information to a corresponding one according to the second website server address The second website server records the corresponding first routing information in the session routing table, and sends the corresponding first routing information to other load balancers in the load balancing cluster for synchronous update.

Optionally, the session management device further includes:

A routing module, configured to route the user request information to a corresponding first website server according to the first website server address when the address of the first website server is detected.

Optionally, the receiving module is specifically used for:

Receive user request information routed by the network management system according to the open shortest path first OSPF network protocol.

Optionally, the session management device further includes:

A timing checking module, configured to regularly check whether the web server in the web server cluster corresponding to the load balancing cluster is available;

The second processing module is configured to replace the second routing information corresponding to the unavailable website server in the session routing table with the third routing information corresponding to the backup website server when it is unavailable, and The replacement information is sent to other load balancers in the load balancing cluster for synchronous update.

Optionally, the second processing module includes:

Generate submodules for generating exception report information when unavailable;

The replacement submodule is configured to replace the unavailable second routing information corresponding to the website server with third routing information corresponding to the backup website server in the session routing table according to the abnormality report information.

Optionally, the session management device further includes:

A synchronous update module, configured to synchronously update the local session routing table when receiving fourth routing information or update information sent by other load balancers in the load balancing cluster.

Optionally, the synchronous update module includes:

Adding a submodule, configured to add the fourth routing information to the local session routing table when receiving the fourth routing information sent by other load balancers in the load balancing cluster;

The first processing sub-module is configured to, when receiving update information sent by other load balancers in the load balancing cluster, search for the fifth corresponding unavailable website server in the local session routing table according to the update information. Routing information, and modifying the fifth routing information to the sixth routing information of the standby website server corresponding to the unavailable website server in the update information.

The present invention also provides a load balancer, which is applied in a load balancing cluster, including: the above-mentioned session management device.

The beneficial effects of above-mentioned technical scheme of the present invention are as follows:

In the above solution, the session management method retrieves the corresponding first website server address by receiving the user request, and if it is not retrieved, obtains a second website server address according to the load balancing strategy for forwarding, and registers the address in the local session routing table The relevant routing information is recorded in , which realizes the user's session request and session maintenance function; at the same time, the newly recorded relevant routing information is sent to other load balancers in the same load balancing cluster for synchronous update, ensuring that the same user can use the , its request can be accurately forwarded to the website server with its session information, and it supports the linear expansion of the load balancing cluster to achieve high availability of the load balancing device, ensure the smooth expansion of the system, and provide users with better interactive use experience.

Description of drawings

FIG. 1 is a functional schematic diagram of each protocol layer in the prior art;

FIG. 2 is a schematic diagram of a four-layer load balancing process in the prior art;

FIG. 3 is a schematic diagram of a seven-layer load balancing process in the prior art;

FIG. 4 is a schematic diagram of an active/standby load balancing architecture in the prior art;

FIG. 5 is a schematic flowchart of a session management method according to Embodiment 1 of the present invention;

FIG. 6 is a schematic diagram of a load balancing system architecture according to Embodiment 2 of the present invention;

FIG. 7 is a schematic structural diagram of a session management device according to Embodiment 2 of the present invention;

FIG. 8 is a schematic flow diagram of a load balancing system according to Embodiment 2 of the present invention;

FIG. 9 is a schematic diagram of synchronous update of session routing information according to Embodiment 2 of the present invention;

FIG. 10 is a schematic structural diagram of a session management device according to Embodiment 3 of the present invention.

Detailed ways

In order to make the technical problems, technical solutions and advantages to be solved by the present invention clearer, the following will describe in detail with reference to the drawings and specific embodiments.

The present invention provides a variety of solutions for the problem that the load balancing method in the existing technology is likely to cause the loss of user session information and affect the user experience, specifically as follows:

Embodiment one

As shown in Figure 5, the session management method provided by Embodiment 1 of the present invention can be applied to any load balancer in the load balancing cluster, and the session management method includes:

Step 51: Receive user request information;

Step 52: Retrieve the corresponding first website server address in the session routing table according to the user request information;

Step 53: When the first website server address is not retrieved, obtain a second website server address according to the load balancing strategy, and route the user request information to the corresponding second website according to the second website server address The server records the corresponding first routing information into the session routing table, and sends the corresponding first routing information to other load balancers in the load balancing cluster for synchronous update.

Wherein, the user request information may be any user's request to access content, and the load balancing strategy may be any other strategy that can achieve technical goals, such as round robin strategy or minimum connection strategy, which is not limited here.

The session management method provided by Embodiment 1 of the present invention retrieves the corresponding first website server address by receiving a user request, and if it is not retrieved, obtains a second website server address according to the load balancing strategy for forwarding, and the local The relevant routing information is recorded in the session routing table, which realizes the user's session request and session maintenance function; at the same time, the newly recorded relevant routing information is sent to other load balancers in the same load balancing cluster for synchronous update, ensuring the same When the user uses it again, its request can be accurately forwarded to the website server with its session information, and supports the linear expansion of the load balancing cluster to achieve high availability of the load balancing device, ensure the smooth expansion of the system, and provide users with better interactive experience.

Correspondingly, the session management method further includes: when detecting the address of the first website server, routing the user request information to the corresponding first website server according to the address of the first website server.

In order to make the user experience better, before retrieving the corresponding first website server address in the session routing table according to the user request information, the session management method further includes: performing the user request information according to preset rules preprocessing.

Specifically, the step of preprocessing the user request information according to preset rules includes: receiving and shielding processing according to the source address IP of the client in the user request information; or, according to the IP address of the user request information The request content is received and shielded; or, when the request type in the user request information is a predetermined type, the user request information is directly forwarded to the corresponding predetermined website server interface for predetermined operation processing.

Wherein, the step of receiving user request information specifically includes: receiving user request information routed by the network management system according to the Open Shortest Path First (OSPF) network protocol.

Further, the session management method further includes: periodically checking whether the website server in the website server cluster corresponding to the load balancing cluster is available; The second routing information corresponding to the server is replaced with the third routing information of the standby website server corresponding thereto, and the replacement information is sent to other load balancers in the load balancing cluster for synchronous update.

Specifically, when it is unavailable, the step of replacing the second routing information corresponding to the unavailable website server with the third routing information corresponding to the standby website server in the session routing table includes: When unavailable, abnormal report information is generated; according to the abnormal report information, the second routing information corresponding to the unavailable website server is replaced with the third routing information corresponding to the standby website server in the session routing table.

Corresponding to the situation that this load balancer also needs to be updated synchronously, the session management method further includes: when receiving the fourth routing information or update information sent by other load balancers in the load balancing cluster, performing The above session routing table is updated synchronously.

Specifically, when receiving fourth routing information or update information sent by other load balancers in the load balancing cluster, the step of synchronously updating the local session routing table includes: receiving the load When balancing the fourth routing information sent by other load balancers in the cluster, adding the fourth routing information to the local session routing table; receiving the fourth routing information sent by other load balancers in the load balancing cluster When updating information, look up the fifth routing information of the corresponding unavailable website server in the local session routing table according to the updating information, and modify the fifth routing information to be the same as the unavailable website server in the updating information. The sixth routing information of the standby website server corresponding to the website server.

Considering the actual situation, in this embodiment, the step of obtaining a second website server address according to the load balancing strategy includes: obtaining a second website server address according to the polling strategy; or obtaining a second website server address according to the minimum connection strategy server address.

Embodiment two

The session management solution provided by Embodiment 2 of the present invention will be described in detail below with reference to FIG. 6 to FIG. 9 .

As shown in FIG. 6 , the architecture of the entire system in the solution of Embodiment 2 of the present invention mainly involves load balancing clusters and Session Management Devices (SMDs) based on OSPF (OpenShortest Path First) high-speed networks.

The specific instructions are as follows:

load balancing cluster

Build a high-speed network environment based on the OSPF network protocol, and implement equal-cost routing of user requests to each load balancer.

The OSPF protocol divides the autonomous system into different areas (Area). Areas logically divide routers into different groups, and each group is identified by an area number (Area ID). Multiple load balancers can be set up in a region to form a cluster. Requests are routed at equal cost within the region, and requests are evenly distributed to each load balancer. At the same time, multiple regions (clusters) can be established as needed.

Session session management device (SMD)

As shown in Figure 7, SMD contains five modules: request receiving interface module, session route retrieval module, session route synchronization module, request forwarding module and WEB (website) server detection module, and each module coordinates with each other to ensure that users The request can be accurately forwarded to the WEB server with its session information, as shown in Figure 8:

Step 81: The user sends a request, and the request is forwarded to a load balancer in the load balancing cluster through the core router;

Step 82: The load balancer transfers the received request to the request receiving interface module of the session management device (SMD);

Step 83: After the request receiving interface module receives the request, it analyzes the content of the request, and can classify and process the request according to the set corresponding strategy, and forwards the request to the session route retrieval module after processing. ;

Step 84: The session routing retrieval module retrieves the session routing table according to the requested session information, and performs corresponding processing according to the retrieval result, if the corresponding session information is retrieved, enter step 85, if not retrieved, enter step 86;

Step 85: The session routing retrieval module sends the request and the retrieved routing information to the request forwarding module, and enters step 88;

Step 86: The session route retrieval module forwards the retrieval result and the request to the session route synchronization module;

Step 87: The session routing synchronization module allocates a WEB server for the request according to the load balancing strategy, and then, step 871: records the relevant routing information of the session (the WEB server allocated) into the local session routing table, and updates it synchronously Go to the SMD of other nodes in the load balancing cluster; step 872: send the distributed WEB server information and request to the request forwarding module, and enter step 88;

Step 88: The request forwarding module routes the request to its corresponding WEB server according to the routing information;

Step 89: the WEB server processes the received request and returns the processing result to the corresponding load balancer;

Step 810: the load balancer returns the received processing result to the client (user);

Step 811: the WEB service detection module regularly checks whether the WEB server is available (detection service status);

Step 812: if it is found that the WEB server is unavailable (abnormal service), then the information is given to the session routing synchronization module;

Step 813: the relevant routing information of all this WEB server (the WEB server of service abnormality in step 812) in the routing table can be revised into the address of the standby WEB server of this WEB server by the session routing synchronous module; The standby WEB server can rely on the Session of WEB server The replication function saves the session information of the failed WEB server, so that subsequent requests will be routed to the standby WEB server to ensure that user requests can be processed normally.

The five modules in the session management device (SMD) are described in detail below:

Request Receive Interface Module

Responsible for receiving user request information from the load balancer, and classify the requests according to the corresponding policies set:

1. Can receive and shield processing according to the source IP of the client.

2. Can receive and block processing according to the content of the request.

3. Specific requests can be directly forwarded to a specific WEB server interface for specific operation processing.

Session Route Retrieval Module

Search the session routing table according to the requested session information, determine whether the request is a new request, and forward it to other modules in the device for processing according to the search result.

Among them, the data structure of the routing table is shown in the following table:

Field Name field description Source_IP Requested client IP address SessionID Requested SessionID information Dest_IP IP address of the web server Dest_Port Port information of the WEB server URL_PATH Context root information for application access

Session Routing Synchronization Module

Maintain the local routing table information according to the request information of the session routing retrieval module and the WEB server detection module, and send the routing table information to other load balancers (LB) in the load balancing cluster through MultiCast (multicast transmission) or IP communication protocol members, so that they can modify the local routing table information synchronously, as shown in Figure 9.

request forwarding module

According to the retrieval result of the session routing retrieval module, the request is forwarded to the WEB server with the corresponding session information.

1. If the session route retrieval module retrieves the session record with the request, it forwards it to the corresponding WEB server according to the record information in the routing table.

2. If the session route retrieval module does not retrieve the session record of the request, normal forwarding is performed according to the load balancing policy set by the load balancer.

WEB service detection module

The module regularly detects the availability of the WEB server according to the set detection period, maintains the local routing table information according to the feedback result, and calls the session routing synchronization module to update the load balancing cluster routing information synchronously.

Based on the Session replication function of the WEB server cluster, if this module detects that a WEB server fails, it will update the session routing table data associated with the WEB server to point to the backup node server to continue providing services, ensuring that no users are lost session information.

It can be seen from the above that the session management solution provided by the second embodiment of the present invention realizes the synchronous sharing of session routing information in the load balancing cluster through the session management device (SMD), ensuring that user requests can be accurately forwarded to the WEB with its session information. On the server, and supports the linear expansion of the load balancing cluster, realizes the high availability of the load balancing equipment, and ensures the smooth expansion capability of the system.

To sum up, Embodiment 2 of the present invention provides a seven-layer load balancing cluster architecture that can support distributed horizontal expansion without losing user session information, and realizes that load balancing devices can be linearly expanded according to production needs The purpose; and it can effectively manage Session sessions, support session retention, and ensure that session information is not lost; realize high availability of load balancing equipment, and ensure stable and efficient operation of the information system.

Embodiment three

As shown in FIG. 10, the session management device provided by Embodiment 3 of the present invention can be applied to any load balancer in the load balancing cluster, and the session management device includes:

A receiving module 101, configured to receive user request information;

A retrieval module 102, configured to retrieve the corresponding first website server address in the session routing table according to the user request information;

The first processing module 103 is configured to obtain a second website server address according to a load balancing strategy when the first website server address is not retrieved, and route the user request information to the second website server address according to the second website server address The corresponding second website server records the corresponding first routing information into the session routing table, and sends the corresponding first routing information to other load balancers in the load balancing cluster for synchronous update.

Wherein, the user request information may be any user's request to access content, and the load balancing strategy may be any other strategy that can achieve technical goals, such as round robin strategy or minimum connection strategy, which is not limited here.

The session management device provided in Embodiment 3 of the present invention retrieves the corresponding first website server address by receiving a user request, and if not retrieved, obtains a second website server address according to the load balancing strategy and forwards it to the local The relevant routing information is recorded in the session routing table, which realizes the user's session request and session maintenance function; at the same time, the newly recorded relevant routing information is sent to other load balancers in the same load balancing cluster for synchronous update, ensuring the same When the user uses it again, its request can be accurately forwarded to the website server with its session information, and supports the linear expansion of the load balancing cluster to achieve high availability of the load balancing device, ensure the smooth expansion of the system, and provide users with better interactive experience.

Correspondingly, the session management device further includes: a routing module, configured to route the user request information to the corresponding first website server according to the first website server address when the address of the first website server is detected .

In order to improve user experience, the session management method further includes: a preprocessing module, configured to preprocess the user request information according to preset rules before the first processing module performs operations.

Specifically, the preprocessing module includes: a second processing submodule for receiving and shielding processing according to the source address IP of the client in the user request information; or, a third processing submodule for processing according to the user request The request content in the request information is received and shielded; or, the fourth processing submodule is used to directly forward the user request information to the corresponding predetermined website when the request type in the user request information is a predetermined type The server interface performs predetermined operation processing.

Wherein, the receiving module is specifically configured to: receive user request information routed by the network management system according to the open shortest path first OSPF network protocol.

Further, the session management device further includes: a timing checking module, configured to periodically check whether a web server in the web server cluster corresponding to the load balancing cluster is available; a second processing module, configured to: In the session routing table, the second routing information corresponding to the unavailable website server is replaced with the third routing information of the standby website server corresponding thereto, and the replacement information is sent to other loads in the load balancing cluster The equalizer is updated synchronously.

Specifically, the second processing module includes: a generating submodule, configured to generate abnormal report information when unavailable; a replacement submodule, configured to generate all abnormal report information that will be unavailable in the session routing table according to the abnormal report information The second routing information corresponding to the website server is replaced with the third routing information corresponding to the standby website server.

Corresponding to the situation that the load balancer also needs to be updated synchronously, the session management device further includes: a synchronous update module, configured to receive fourth routing information or update information sent by other load balancers in the load balancing cluster , the local session routing table is synchronously updated.

Specifically, the synchronous update module includes: an adding submodule, configured to add the fourth routing information to the local when receiving the fourth routing information sent by other load balancers in the load balancing cluster In the session routing table; the first processing submodule is configured to, when receiving update information sent by other load balancers in the load balancing cluster, search the local session routing table for corresponding The fifth routing information of the unavailable website server, and modifying the fifth routing information to the sixth routing information of the standby website server corresponding to the unavailable website server in the update information.

Considering the actual situation, in this embodiment, the first processing module includes: a first obtaining submodule, configured to obtain a second website server address according to a polling strategy; or, a second obtaining submodule, configured to obtain a second website server address according to a minimum The connection strategy acquires a second website server address.

It should be noted that, all the implementation embodiments of the above session management method are applicable to the embodiments of the session management device, and can also achieve the same technical effect.

The session management device provided in the third embodiment of the present invention can be used to improve the load balancer in the existing load balancing cluster, so as to realize the function of the session management device in the third embodiment of the present invention.

What has been described above is a preferred embodiment of the present invention. It should be pointed out that for those skilled in the art, some improvements and modifications can also be made without departing from the principle of the present invention. These improvements and modifications should also be considered as Be the protection scope of the present invention.

Claims (11)

1. a kind of conversation managing method, applied to any load balancer in load balancing cluster characterized by comprising

Receive user request information；

Corresponding first Website server address is retrieved in session routing table according to user request information；

When not retrieving the first Website server address, with obtaining one second Website server according to load balancing Location, and the user request information is routed to by corresponding second Website server according to second Website server address, Corresponding first routing iinformation is recorded in the session routing table, corresponding first routing iinformation is sent to described Other load balancers in load balancing cluster synchronize update；

Whether the Website server in regular check Website server cluster corresponding with the load balancing cluster can be used；

When unavailable, then by the corresponding secondary route information of the not available Website server in the session routing table It is changed to the third routing iinformation of corresponding spare Website server, and replacement information is sent to the load balancing collection Other load balancers in group synchronize update；

It is described when unavailable, then by the corresponding secondary route of the not available Website server in the session routing table Change dump be corresponding spare Website server third routing iinformation the step of include:

When unavailable, exception reporting information is generated；

According to the exception reporting information by the not available Website server corresponding second in the session routing table Routing iinformation is changed to the third routing iinformation of corresponding spare Website server.

2. conversation managing method as described in claim 1, which is characterized in that the conversation managing method further include:

When detecting the first Website server address, the user is requested according to first Website server address Information router is to corresponding first Website server.

3. conversation managing method as described in claim 1, which is characterized in that the step of reception user request information is specific Are as follows:

Receive the user request information that network management is routed according to Open Shortest Path First ospf network agreement.

4. conversation managing method as described in claim 1, which is characterized in that the conversation managing method further include:

When receiving the 4th routing iinformation or more new information that other load balancers in the load balancing cluster are sent, Update is synchronized to the local session routing table.

5. conversation managing method as claimed in claim 4, which is characterized in that described in receiving the load balancing cluster Other load balancers send the 4th routing iinformation or more new information when, the local session routing table is synchronized The step of update includes:

When receiving four routing iinformation that other load balancers in the load balancing cluster are sent, by the 4th tunnel It is increased newly by information into the local session routing table；

When receiving the more new information that other load balancers in the load balancing cluster are sent, according to the more new information Search the 5th routing iinformation of corresponding unavailable Website server in the local session routing table, and by the 5th tunnel The 6th of spare Website server corresponding with the unavailable Website server in the more new information the is revised as by information Routing iinformation.

6. a kind of session management device, applied to any load balancer in load balancing cluster characterized by comprising

Receiving module, for receiving user request information；

Retrieval module, for retrieving corresponding first Website server address in session routing table according to user request information；

First processing module, for being obtained according to load balancing when not retrieving the first Website server address One second Website server address, and the user request information is routed to by correspondence according to second Website server address The second Website server, corresponding first routing iinformation is recorded in the session routing table, by described corresponding first Other load balancers that routing iinformation is sent in the load balancing cluster synchronize update；

Regular check module, for the website clothes in regular check Website server cluster corresponding with the load balancing cluster Whether business device can be used；

Second processing module is used for when unavailable, then by the not available Website server in the session routing table Corresponding secondary route change dump is the third routing iinformation of corresponding spare Website server, and will replacement information hair Other load balancers into the load balancing cluster are sent to synchronize update；

The Second processing module includes:

Submodule is generated, for generating exception reporting information when unavailable；

Submodule is replaced, for taking the not available website in the session routing table according to the exception reporting information The corresponding secondary route change dump of business device is the third routing iinformation of corresponding spare Website server.

7. session management device as claimed in claim 6, which is characterized in that the session management device further include:

Routing module, for when detecting the first Website server address, according to first Website server address The user request information is routed into corresponding first Website server.

8. session management device as claimed in claim 6, which is characterized in that the receiving module is specifically used for:

Receive the user request information that network management is routed according to Open Shortest Path First ospf network agreement.

9. session management device as claimed in claim 6, which is characterized in that the session management device further include:

Synchronized update module, in the 4th routing for receiving other load balancers transmission in the load balancing cluster When information or more new information, update is synchronized to the local session routing table.

10. session management device as claimed in claim 9, which is characterized in that the synchronized update module includes:

Newly-increased submodule, in the 4th routing iinformation for receiving other load balancers transmission in the load balancing cluster When, the 4th routing iinformation is increased newly into the local session routing table；

First processing submodule, in the more new information for receiving other load balancers transmission in the load balancing cluster When, according to the 5th routing of corresponding unavailable Website server in the session routing table for updating information searching local Information, and the 5th routing iinformation is revised as corresponding standby with the unavailable Website server in the more new information With the 6th routing iinformation of Website server.

11. a kind of load balancer is applied in load balancing cluster characterized by comprising such as claim 6 to 10 times Session management device described in one.