Method for implementing long connection changeover of network

Abstract

The invention discloses a method for implementing the switching of long network connection, comprising: establishing at least a virtual server corresponding to a server group with the same servicing function, composed of at least a real server; setting an identification word for the virtual server to identify the state change of the real server in the server group; according to the identification word, judging if the state of the real server changes: if the state is normal, establishing the connection between a client and the real server; otherwise, implementing the switching of long connection according to the identification word. The invention can still evenly allocate the whole flow to different servers as the state of the real server changes and assure the implementation of the switching of long connection by network load balancing equipment after the state of the real server is normal.

Description

technical field [0001] The invention relates to the technical field of network connection, in particular to a method for realizing network long connection switching. Background technique [0002] With the development of network technology, network construction and application are advancing by leaps and bounds, network users continue to increase, and network load balancing equipment is also increasingly used in networks of all walks of life. Sharing, that is, using multiple algorithms to evenly distribute the total access traffic to different servers. And there is also a corresponding health detection mechanism. If a real server is unavailable, the traffic connected to this device will be shared to other servers. When this server can run normally again, the load balancing device will Redistribute network traffic to the server, but not traffic that was connected to the server before the server became unavailable. In some special fields (such as banking, securities, etc.), th...

AI Technical Summary

Problems solved by technology

[0003] The current load balancing equipment only realizes the traffic sharing. When the server changes between available -> unavailable -> available, it can reconnect part of the traffic to the server that returns to the normal state to ensure that all The server load is balanced, but it is impossible to reconnect the original traffic to the server that returns to normal state. In this way, after a server with load fails, all the load is transferred to other servers. When the failed server works again Afterwards, since no new long connections are generated (because they are all long connections), the server will always be in a state of no load, just like a dummy

This makes it impossible to use in some application areas

Images