[go: up one dir, main page]

CN101938502B - Server cluster system and load balancing method - Google Patents

Server cluster system and load balancing method Download PDF

Info

Publication number
CN101938502B
CN101938502B CN 200910089304 CN200910089304A CN101938502B CN 101938502 B CN101938502 B CN 101938502B CN 200910089304 CN200910089304 CN 200910089304 CN 200910089304 A CN200910089304 A CN 200910089304A CN 101938502 B CN101938502 B CN 101938502B
Authority
CN
China
Prior art keywords
instant message
message request
module
server
request
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related
Application number
CN 200910089304
Other languages
Chinese (zh)
Other versions
CN101938502A (en
Inventor
程渤
章洋
叶波
黄丽婷
陈俊亮
王月
刘习贺
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing University of Posts and Telecommunications
Original Assignee
Beijing University of Posts and Telecommunications
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing University of Posts and Telecommunications filed Critical Beijing University of Posts and Telecommunications
Priority to CN 200910089304 priority Critical patent/CN101938502B/en
Publication of CN101938502A publication Critical patent/CN101938502A/en
Application granted granted Critical
Publication of CN101938502B publication Critical patent/CN101938502B/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Computer And Data Communications (AREA)

Abstract

本发明涉及一种服务器集群系统和负载均衡方法,以解决现有服务器集群系统没有考虑用户终端请求相同业务的问题。本发明提供的服务器集群系统包括负载均衡子系统和服务器集群,所述负载均衡子系统按照既定方法选择处理即时消息请求的目标服务器。所述负载均衡子系统包括:请求接收模块、请求转发模块、响应接收模块、响应转发模块、HTTP解析模块、内存管理模块、服务器管理模块、目标服务器选择模块一、目标服务器选择模块二、目标服务器选择模块三和状态监控模块。本发明还提供了一种负载均衡方法。使用本发明能为不同类型的消息请求合理地选择目标服务器。

Figure 200910089304

The invention relates to a server cluster system and a load balancing method to solve the problem that the existing server cluster system does not consider that user terminals request the same service. The server cluster system provided by the present invention includes a load balancing subsystem and a server cluster, and the load balancing subsystem selects a target server for processing instant message requests according to a predetermined method. The load balancing subsystem includes: request receiving module, request forwarding module, response receiving module, response forwarding module, HTTP parsing module, memory management module, server management module, target server selection module 1, target server selection module 2, target server Select module three and the status monitoring module. The invention also provides a load balancing method. The invention can reasonably select target servers for different types of message requests.

Figure 200910089304

Description

A kind of server cluster system and load-balancing method
Technical field
The present invention relates to a kind of server cluster system and load-balancing method.
Background technology
Along with the development of Internet technology, the type of service variation that becomes, the multimedia communication of the multiple business such as developing into nowadays from the data communication of single business can support voice, video.For the system that is formed by the separate unit server, because the restriction of the aspects such as the central processing unit of separate unit server, input/output interface processing speed, the server cluster system that is comprised of multiple servers is the substitute is in the requirement that can't satisfy the data volume of rapid growth and process simultaneously multiple business.
Server cluster system requires a kind of high-efficient carrier equalization methods reasonably to be dispensed to multiple servers to guarantee a plurality of message request.Existing load-balancing method based on weights polling dispatching algorithm takes full advantage of the resource of server cluster system according to the instant message request that the is not all select target server of server performance; The load-balancing method of existing dialogue-based numbering (Session ID) can be identified the different instant message requests that same user terminal sends, these instant message requests are processed by same station server, saved the actions such as repetition identification, parameter transmission.But above-mentioned load-balancing method has all been ignored the situation of user terminal requests identical services.
Summary of the invention
Do not consider the problem of user terminal requests identical services in order to solve above-mentioned existing server cluster system, the invention provides a kind of server cluster system and load-balancing method, use this server cluster system and load-balancing method to select only destination server for dissimilar instant message request.
Technical scheme of the present invention is as follows:
The invention provides a kind of server cluster system.This system comprises load balancing subsystem and server cluster, and described load balancing subsystem selects to process the destination server of instant message request according to established methodology, and described established methodology is: receive the instant message request; The analyzing instant messages request judges whether the message header of the instant message request after resolving contains the path of destination server; If the message header of the instant message request after the described parsing does not contain the path of destination server, judge whether the message body of the instant message request after resolving contains professional numbering; If the message body of the instant message request after the described parsing contains professional numbering, according to described professional numbering select target server, encapsulate instant message request after the described parsing according to the host-host protocol of described destination server support, the instant message request after the parsing that has encapsulated of sending is to described destination server; If the message body of the instant message request after the described parsing does not contain professional numbering or according to described professional numbering select target server failure, judge whether the message header of the instant message request after the described parsing contains session number; If the message header of the instant message request after the described parsing contains session number, according to described session number select target server, encapsulate instant message request after the described parsing according to the host-host protocol of described destination server support, the instant message request after the parsing that has encapsulated of sending is to described destination server; If the message header of the instant message request after the described parsing does not contain session number or according to described session number select target server failure, according to weights polling dispatching algorithm select target server, encapsulate instant message request after the described parsing according to the host-host protocol of described destination server support, the instant message request after the parsing that has encapsulated of sending is to described destination server; If the message header of the instant message request after the described parsing contains the path of destination server, encapsulate instant message request after the described parsing according to the host-host protocol of destination server support, the instant message request after the parsing that has encapsulated of sending is to described destination server; Reception is from the reception response of described destination server; Encapsulate described reception response by HTTP, and the reception that transmission has encapsulated responds the extremely transmitting terminal of described instant message request; It is characterized in that, described load balancing subsystem comprises:
The request receiving module receives the instant message request;
The HTTP parsing module, the message header of analyzing instant messages request and message body;
The request forwarding module encapsulates instant message request after the described parsing according to the host-host protocol of destination server support, and the instant message request after the parsing that has encapsulated of sending is to described destination server;
The response receiver module, the reception response that the receiving target server sends;
The response forwarding module encapsulate described reception response according to HTTP, and the reception that transmission has encapsulated responds to the transmitting terminal of instant message request;
Memory management module, the memory source of distribution and load management equalization subsystem;
Server management module configures described server cluster and the parameter that server in the described server cluster is set;
Destination server is selected module one, the business that comprises in the message body according to the instant message request after described parsing numbering select target server;
Destination server is selected module two, the session number select target server that comprises in the message header according to the instant message request after the described parsing;
Destination server is selected module three, according to the server performance select target server in the described server cluster;
Monitoring module is for the operating state of obtaining described each station server of server cluster.
Above-mentioned server cluster system also comprises the reservation message ADMINISTRATION SUBSYSTEM, and described reservation message ADMINISTRATION SUBSYSTEM comprises:
The message sink module is for the lastest imformation that receives non-instant message request or non-instant message request;
Message storage module is for the lastest imformation of storing described non-instant message request or described non-instant message request;
Data management module is for detection of the processing time of non-instant message request in the described message storage module and the non-instant message request that is used for upgrading described message storage module;
The message trigger module is converted into the instant message request in the processing time of described non-instant message request with described non-instant message request, sends described instant message request to described load balancing subsystem.
In the above-mentioned server cluster system, described message storage module comprises:
The database submodule is used for storage from the non-instant message request of message sink module or the lastest imformation of non-instant message request;
The data buffer storage submodule is used for storage from the non-instant message request of database submodule or from the lastest imformation of the non-instant message request of message sink module.
In the above-mentioned server cluster system, the processing time of non-instant message request refers in the described message storage module of described detection:
A, described data management module are accessed once described database submodule every given time X, judge that the non-instant message request whether reservation is arranged in the described database submodule is in constantly processing of access;
If there is the non-instant message request of reservation constantly to process in access in the described database submodule of B, described data management module is sent to described message trigger module with the non-instant message request of described reservation;
If the non-instant message request of reservation is not in the processing of the access moment in the described database submodule of C, described data management module is extracted into described data buffer storage submodule with constantly and next time accessing the non-instant message request of processing between the moment about described access in advance in the described database submodule;
D, described data management module are accessed once described data buffer storage submodule every given time Y, judge that the non-instant message request whether reservation is arranged in the described data buffer storage submodule is in constantly processing of access;
If there is the non-instant message request of reservation constantly to process in access in the described data buffer storage submodule of E, described data management module is sent to described message trigger module with the non-instant message request of described reservation;
If in the described data buffer storage submodule of F not the non-instant message request of reservation constantly process in access, described data management module waits for that next access accesses described data buffer storage submodule constantly;
Described given time Y is less than described given time X.
In the above-mentioned server cluster system, the non-instant message request in the described message storage module of described renewal refers to:
A, described message sink module receive the lastest imformation of non-instant message request;
B, described data management module are accessed described data buffer storage submodule, search the non-instant message request that whether exists described lastest imformation corresponding in the described data buffer storage submodule;
If there be non-instant message request corresponding to described lastest imformation in the described data buffer storage submodule of C, described data management module reads described lastest imformation to described data buffer storage submodule, replacing needs the content that is updated in non-instant message request corresponding to lastest imformation described in the described data buffer storage submodule, and sends to described message sink module and to be updated successfully indication;
If there be not non-instant message request corresponding to described lastest imformation in the described data buffer storage submodule of D, described data management module is accessed described database submodule, searches the non-instant message request that whether exists described lastest imformation corresponding in the described database submodule;
If there be non-instant message request corresponding to described lastest imformation in the described database submodule of E, described data management module reads described lastest imformation to described database submodule, replacing needs the content that is updated in non-instant message request corresponding to lastest imformation described in the described database submodule, and sends to described message sink module and to be updated successfully indication;
If there be not non-instant message request corresponding to described lastest imformation in the described database submodule of F, described data management module sends to described message sink module and upgrades unsuccessfully indication.
The user terminal that the transmitting terminal of this instant message request is asked for directly transferring immediate news or the user terminal that sends non-instant message request.
Beneficial effect of the present invention is:
(1) utilizes professional numbering select target server, the instant message of the identical services that calls request is processed by same destination server, improved treatment effeciency;
(2) merged according to business numbering select target server, according to session number select target server and according to multiple load-balancing methods such as weights polling dispatching algorithm select target servers, can select best destination server for dissimilar instant message request;
(3) the instant message request can not only be processed, non-instant message request can also be processed.
By reference to the accompanying drawings, other characteristics of the present invention and advantage can be from below by becoming clearer the explanation of giving an example the preferred implementation that principle of the present invention is made an explanation.
Description of drawings
Fig. 1 illustrates the server cluster system Organization Chart that does not contain the reservation message ADMINISTRATION SUBSYSTEM;
Fig. 2 illustrates the server cluster system Organization Chart that contains the reservation message ADMINISTRATION SUBSYSTEM;
Fig. 3 illustrates the load-balancing method flow chart.
Embodiment
Below in conjunction with accompanying drawing, embodiments of the present invention are illustrated.
Embodiment one, and server cluster system as shown in Figure 1.User terminal 100 transfers immediate news and asks to load balancing subsystem 101.This instant message request is the HTTP request.Load balancing subsystem 101 receives this instant message request, and selects the destination server 108 of this instant message request of processing according to set load-balancing method.
The present embodiment has provided one destination server 108, but in actual applications, destination server is not that changeless, dissimilar instant message request may corresponding different destination servers.
The functional module of load balancing subsystem 101 as shown in Figure 1.Load balancing subsystem 101 comprises that request receiving module 211, request forwarding module 212, response receiver module 213, response forwarding module 214, HTTP parsing module 215, memory management module 216, server management module 217, destination server select module 1, destination server to select module 2 219, destination server to select module 3 220 and monitoring module 221.
The instant message request that request receiving module 211 receives from user terminal 100.
HTTP parsing module 215 is resolved this instant message request, and this instant message request comprises request header and request body.According to the specification documents RFC2626 of HTTP, the message header of HTTP request comprises the contents such as session number and destination server information, and the message body of HTTP request comprises professional numbering and request entity information.If the instant message request after resolving comprises the routing information of destination server, the instant message request after the parsing is sent to request forwarding module 212.If the instant message request after resolving does not comprise the routing information of destination server, the instant message request after the parsing is sent to destination server and selects module 1, destination server to select module 2 219 or destination server to select module 3 220.
The business numbering select target server that comprises in the message body after destination server selects module 1 according to 215 parsings of HTTP parsing module.The session number select target server that comprises in the message header after destination server selects module 2 219 according to 215 parsings of HTTP parsing module.Destination server selects module 3 220 according to the server performance select target server in the server cluster.
The host-host protocol that request forwarding module 212 is supported according to the destination server 108 of selecting encapsulates the instant message request after this parsings, and the instant message request after the parsing that encapsulated of transmission is to destination server 108.
The reception response that response receiver module 213 receiving target servers 108 send.Response forwarding module 214 encapsulates this reception response according to HTTP, and the reception response that transmission has encapsulated is to the user terminal 100 that sends this instant message request.
The memory source of memory management module 216 distribution and load management equalization subsystem 101.
The number of units of server and the host-host protocol that server initial parameter and server are supported in the server cluster is set in the server management module 217 configuration server clusters.
Monitoring module 221 obtains the operating state of each station server in the server cluster, but according to the performance number of this operating state calculation server.
Embodiment two, and server cluster system as shown in Figure 2.Server cluster system outside the server cluster 107, also comprises reservation message ADMINISTRATION SUBSYSTEM 102 except load balancing subsystem 101 among this embodiment.Wherein, reservation message ADMINISTRATION SUBSYSTEM 102 is comprised of four functional modules: message sink module 103, message storage module 104, data management module 105 and message trigger module 106.Wherein, message storage module 104 is comprised of database submodule 1041 and data buffer storage submodule 1042.
The non-instant message request that message sink module 103 reception user terminals 200 send or the lastest imformation of non-instant message request.The lastest imformation of this non-instant message request or non-instant message request has comprised the processing time of non-instant message request.This non-instant message request is converted into the instant message request in this processing time.
Message storage module 104 is used for non-instant message request that storage user terminal 200 sends or the lastest imformation of non-instant message request.
Data management module 105 is for detection of the processing time of non-instant message request in the message storage module 104 and the non-instant message request that is used for updating message memory module 104.
Message trigger module 106 is converted into the instant message request in the processing time of non-instant message request with non-instant message request, sends this instant message request to load balancing subsystem 101.
The process in the processing time of non-instant message request is as follows in the data management module 105 detect-message memory modules 104: data management module 105 is set up two threads, one of them thread judges that every database submodule 1041 of given time X access the non-instant message request whether reservation is arranged in this database submodule 1041 is in constantly processing of this access.If there is the non-instant message request of reservation constantly to process in this access in the database submodule 1041, this thread reads the non-instant message request of this reservation to message trigger module 106; If the non-instant message request of not preengaging in the database submodule 1041 is processed constantly in this access, above-mentioned thread will ask that about the visit the moment and the non-instant message request of next time processing between the access constantly are sent to data buffer storage submodule 1042 in the database submodule 1041 in advance.Another thread of data management module 105 is accessed once this data buffer storage submodule 1042 every given time Y, judges that the non-instant message request whether reservation is arranged in this data buffer storage submodule 1042 is in constantly processing of this access.If there is the non-instant message request of reservation constantly to process in this access in the data buffer storage submodule 1042, this thread reads the non-instant message request of this reservation to message trigger module 106; If the non-instant message request of reservation is not in constantly processing of this access in the data buffer storage submodule 1042, next access of this thread waits is visit data cache sub-module 1042 constantly.Above-mentioned given time Y is less than described given time X.
The process of non-instant message request is as follows in the data management module 105 updating message memory modules 104: when message sink module 103 receives the lastest imformation of non-instant message request, data management module 105 is visit data cache sub-module 1042 at first, searches the non-instant message request that whether exists this lastest imformation corresponding in the data buffer storage submodule 1042.If there be non-instant message request corresponding to this lastest imformation in the data buffer storage submodule 1042, data management module 105 reads this lastest imformation to data buffer storage submodule 1042, replacing needs the content that is updated in wherein corresponding with this lastest imformation non-instant message request, and sends to message sink module 103 and to be updated successfully indication; If there be not non-instant message request corresponding to this lastest imformation in the data buffer storage submodule 1042, data management module 105 accessing database submodules 1041 are searched the non-instant message request that whether exists this lastest imformation corresponding in the database submodule 1041.If there be non-instant message request corresponding to this lastest imformation in the database submodule 1041, data management module 105 reads this lastest imformation to database submodule 1041, replacing needs the content that is updated in wherein corresponding with this lastest imformation non-instant message request, and sends to message sink module 103 and to be updated successfully indication; If there be not non-instant message request corresponding to this lastest imformation in the database submodule 1041, data management module 105 sends to message sink module 103 and upgrades unsuccessfully indication.
The request receiving module of load balancing subsystem 101 receives the instant message request from reservation message ADMINISTRATION SUBSYSTEM 102, and selects the destination server of this instant message request of processing from server cluster 107.Load balancing subsystem 101 is that the process of this instant message request select target server is the process from the instant message request select target server of user terminal 100 with load balancing subsystem among the embodiment one 101.Destination server sends and receives response to response receiver module 213, and response forwarding module 214 should receive and be sent to user terminal 200 after response encapsulates according to HTTP.Response forwarding module 214 can directly be sent to user terminal 200 with receiving response, also can will receive response by reservation message ADMINISTRATION SUBSYSTEM 102 and be forwarded to user terminal 200.
In this embodiment, the request receiving module of load balancing subsystem 101 also receives instant message request from user terminal 100 except the instant message request from reservation message ADMINISTRATION SUBSYSTEM 102 of receiving.In the present embodiment 101 pairs of load balancing subsystems from the processing procedure of the instant message request of user terminal 100 with 101 pairs of processing procedures from the instant message of user terminal 100 of load balancing subsystem among the embodiment one.
In above-mentioned two kinds of embodiment, the set load-balancing method of load balancing subsystem 101 select target servers as shown in Figure 3.The method starts from step S301.Then, in step S302, the instant message request that request receiving module 211 receives from user terminal 100 or reservation message ADMINISTRATION SUBSYSTEM 102.
In step S303, the 215 analyzing instant messages requests of HTTP parsing module judge whether the message header of the instant message request after resolving contains the path of destination server.
If the result of step S303 is "Yes", then flow process enters step S311; Otherwise enter step S304.
In step S304, HTTP parsing module 215 judges whether the message body of the instant message request after resolving contains professional numbering.
When one of user terminal requests is professional, in the message body of the message request of its transmission, can be endowed a professional numbering.Ask the message body of same professional message request to contain identical business numbering.Such as, above-mentioned business is multimedia conferencing, asks the message body of the message request of same multimedia conferencing to contain identical business numbering.
If the result of step S304 is "Yes", then flow process enters step S305; Otherwise enter step S307.
In step S305, according to business numbering select target server.
This step selects module 1 to finish by destination server.Destination server selection module 1 is searched the server of processing the instant message request with identical services numbering in the cluster server 107.If find this server, destination server selects the instant message request after module 1 will be resolved to be sent to this server; If do not find this server, the instant message request that does not also have server process to cross to have this business numbering in the server cluster 107 is described, destination server selects module 1 to HTTP parsing module 215 signal of giving notice.Select server according to business numbering, the instant message request that will have after the parsing of identical services numbering is dispensed to same station server, has improved the treatment effeciency of server.
When server process has the instant message request of professional numbering, need to search existing result to instant message request with this business numbering.By professional numbering select target server, the instant message request that will have the identical services numbering is sent to same server, avoid the access to the different server of processing the instant message request with this business numbering, improved the efficient of server process instant message request.
In step S306, whether determining step S305 successful select target server.
If the result of step S306 is "Yes", then flow process enters step S311; Otherwise enter step S307.
In step S307, whether contain session number in the message header of the instant message request after 215 judgements of HTTP parsing module are resolved.
Session number (Session ID) refers to a unique identifier that sends the user terminal distribution of message request into each.This identifier is for operations such as parameter transmission between user terminal identity authentication, program state record and the page.
If the result of step S307 is "Yes", then flow process enters step S308; Otherwise enter step S310.
In step S308, according to session number select target server.
This step selects module 2 219 to finish by destination server.Destination server selection module 2 219 is searched the server of processing the instant message request with same session numbering in the cluster server 107.If find this server, destination server selects the instant message request after module 2 219 will be resolved to be sent to this server; If do not find this server, destination server selects module 2 219 to target selection module 3 220 signal of giving notice.Select server according to session number, the message request that same user terminal sends is transferred to same station server processing, avoid this server to carry out the operations such as terminal identity authentication of repetition from the message request of same user terminal.
In step S309, whether determining step S308 successful select target server.
If the result of step S309 is "Yes", then flow process enters step S311; Otherwise enter step S310.
In step S310, according to weights polling dispatching algorithm select target server.
This step selects module 3 220 to finish by destination server.Destination server selects module 3 220 to calculate correspondingly server weights according to the operating state of each station server in the server cluster 107, and by the performance number of server weights calculation server.Destination server selects module 3 220 to dispatch successively each station server according to the performance number order from big to small of server, makes the instant message request after the large server priority treatment of performance number is resolved.According to weights polling dispatching algorithm select target server, reasonably utilized the resource of server cluster system.
After the step S310, flow process enters step S311.
In step S311, request forwarding module 212 encapsulates instant message request after the above-mentioned parsing according to the host-host protocol of the destination server support of selecting, and the instant message request after the parsing that has encapsulated of sending is to the destination server of selecting.
In step S312, response receiver module 213 receives the reception response from destination server.
After the instant message request of the destination server of selecting after receiving the parsing that has encapsulated that request forwarding module 212 sends, send and receive and respond to the load balancing subsystem.
In step S313, response forwarding module 214 receives this reception response and encapsulates this reception response by HTTP, sends the reception that has encapsulated and responds to the transmitting terminal of instant message request.The user terminal 100 that the transmitting terminal of this instant message request is asked for directly transferring immediate news or the user terminal 200 that sends non-instant message request.
Flow process ends at step S314.
The above is preferred embodiment of the present invention only, is not that those of ordinary skills can make various changes and modifications within the scope of the appended claims for restriction protection scope of the present invention.

Claims (5)

1. a server cluster system comprises load balancing subsystem and server cluster, and described load balancing subsystem selects to process the destination server of instant message request according to established methodology, and described established methodology is: receive the instant message request; The analyzing instant messages request judges whether the message header of the instant message request after resolving contains the path of destination server; If the message header of the instant message request after the described parsing does not contain the path of destination server, judge whether the message body of the instant message request after resolving contains professional numbering; If the message body of the instant message request after the described parsing contains professional numbering, according to described professional numbering select target server, encapsulate instant message request after the described parsing according to the host-host protocol of described destination server support, the instant message request after the parsing that has encapsulated of sending is to described destination server; If the message body of the instant message request after the described parsing does not contain professional numbering or according to described professional numbering select target server failure, judge whether the message header of the instant message request after the described parsing contains session number; If the message header of the instant message request after the described parsing contains session number, according to described session number select target server, encapsulate instant message request after the described parsing according to the host-host protocol of described destination server support, the instant message request after the parsing that has encapsulated of sending is to described destination server; If the message header of the instant message request after the described parsing does not contain session number or according to described session number select target server failure, according to weights polling dispatching algorithm select target server, encapsulate instant message request after the described parsing according to the host-host protocol of described destination server support, the instant message request after the parsing that has encapsulated of sending is to described destination server; If the message header of the instant message request after the described parsing contains the path of destination server, encapsulate instant message request after the described parsing according to the host-host protocol of destination server support, the instant message request after the parsing that has encapsulated of sending is to described destination server; Reception is from the reception response of described destination server; Encapsulate described reception response by HTTP, and the reception that transmission has encapsulated responds the extremely transmitting terminal of described instant message request; It is characterized in that, described load balancing subsystem comprises:
The request receiving module receives the instant message request;
The HTTP parsing module, the message header of analyzing instant messages request and message body;
The request forwarding module encapsulates instant message request after the described parsing according to the host-host protocol of destination server support, and the instant message request after the parsing that has encapsulated of sending is to described destination server;
The response receiver module, the reception response that the receiving target server sends;
The response forwarding module encapsulate described reception response according to HTTP, and the reception that transmission has encapsulated responds to the transmitting terminal of instant message request;
Memory management module, the memory source of distribution and load management equalization subsystem;
Server management module configures described server cluster and the parameter that server in the described server cluster is set;
Destination server is selected module one, the business that comprises in the message body according to the instant message request after described parsing numbering select target server;
Destination server is selected module two, the session number select target server that comprises in the message header according to the instant message request after the described parsing;
Destination server is selected module three, according to the server performance select target server in the described server cluster;
Monitoring module is for the operating state of obtaining described each station server of server cluster.
2. described server cluster system according to claim 1 is characterized in that, described server cluster system also comprises the reservation message ADMINISTRATION SUBSYSTEM, and described reservation message ADMINISTRATION SUBSYSTEM comprises:
The message sink module is for the lastest imformation that receives non-instant message request or non-instant message request;
Message storage module is for the lastest imformation of storing described non-instant message request or described non-instant message request;
Data management module is for detection of the processing time of non-instant message request in the described message storage module and the non-instant message request that is used for upgrading described message storage module;
The message trigger module is converted into the instant message request in the processing time of described non-instant message request with described non-instant message request, sends described instant message request to described load balancing subsystem.
3. server cluster system according to claim 2 is characterized in that, described message storage module comprises:
The database submodule is used for storage from the non-instant message request of message sink module or the lastest imformation of non-instant message request;
The data buffer storage submodule is used for storage from the non-instant message request of database submodule or from the lastest imformation of the non-instant message request of message sink module.
4. server cluster system according to claim 3 is characterized in that, the processing time of non-instant message request refers in the described message storage module of described detection:
A, described data management module are accessed once described database submodule every given time X, judge that the non-instant message request whether reservation is arranged in the described database submodule is in constantly processing of access;
If there is the non-instant message request of reservation constantly to process in access in the described database submodule of B, described data management module is sent to described message trigger module with the non-instant message request of described reservation;
If the non-instant message request of reservation is not in the processing of the access moment in the described database submodule of C, described data management module is extracted into described data buffer storage submodule with constantly and next time accessing the non-instant message request of processing between the moment about described access in advance in the described database submodule;
D, described data management module are accessed once described data buffer storage submodule every given time Y, judge that the non-instant message request whether reservation is arranged in the described data buffer storage submodule is in constantly processing of access;
If there is the non-instant message request of reservation constantly to process in access in the described data buffer storage submodule of E, described data management module is sent to described message trigger module with the non-instant message request of described reservation;
If in the described data buffer storage submodule of F not the non-instant message request of reservation constantly process in access, described data management module waits for that next access accesses described data buffer storage submodule constantly;
Described given time Y is less than described given time X.
5. server cluster system according to claim 3 is characterized in that, the non-instant message request in the described message storage module of described renewal refers to:
A, described message sink module receive the lastest imformation of non-instant message request;
B, described data management module are accessed described data buffer storage submodule, search the non-instant message request that whether exists described lastest imformation corresponding in the described data buffer storage submodule;
If there be non-instant message request corresponding to described lastest imformation in the described data buffer storage submodule of C, described data management module reads described lastest imformation to described data buffer storage submodule, replacing needs the content that is updated in non-instant message request corresponding to lastest imformation described in the described data buffer storage submodule, and sends to described message sink module and to be updated successfully indication;
If there be not non-instant message request corresponding to described lastest imformation in the described data buffer storage submodule of D, described data management module is accessed described database submodule, searches the non-instant message request that whether exists described lastest imformation corresponding in the described database submodule;
If there be non-instant message request corresponding to described lastest imformation in the described database submodule of E, described data management module reads described lastest imformation to described database submodule, replacing needs the content that is updated in non-instant message request corresponding to lastest imformation described in the described database submodule, and sends to described message sink module and to be updated successfully indication;
If there be not non-instant message request corresponding to described lastest imformation in the described database submodule of F, described data management module sends to described message sink module and upgrades unsuccessfully indication.
CN 200910089304 2009-07-14 2009-07-14 Server cluster system and load balancing method Expired - Fee Related CN101938502B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN 200910089304 CN101938502B (en) 2009-07-14 2009-07-14 Server cluster system and load balancing method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN 200910089304 CN101938502B (en) 2009-07-14 2009-07-14 Server cluster system and load balancing method

Publications (2)

Publication Number Publication Date
CN101938502A CN101938502A (en) 2011-01-05
CN101938502B true CN101938502B (en) 2013-03-27

Family

ID=43391630

Family Applications (1)

Application Number Title Priority Date Filing Date
CN 200910089304 Expired - Fee Related CN101938502B (en) 2009-07-14 2009-07-14 Server cluster system and load balancing method

Country Status (1)

Country Link
CN (1) CN101938502B (en)

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102055771B (en) * 2011-01-24 2013-06-05 上海红神信息技术有限公司 Device and method for controlling cloud service-oriented multiple concurrent service flow
US8732191B2 (en) * 2011-06-27 2014-05-20 Oracle International Corporation System and method for improving application connectivity in a clustered database environment
CN102436468A (en) * 2011-09-14 2012-05-02 山东中创软件商用中间件股份有限公司 Load balancing method and system based on database cluster
CN102611735B (en) * 2011-12-21 2015-12-09 北京奇虎科技有限公司 A kind of load-balancing method of application service and system
CN103369054B (en) * 2013-07-30 2016-05-18 北京搜狐新媒体信息技术有限公司 A kind of acquisition tasks management method and system
CN103561022A (en) 2013-10-31 2014-02-05 腾讯科技(深圳)有限公司 Voice service access method, related device and voice service system
CN103747274B (en) * 2013-12-18 2016-08-17 北京邮电大学 A kind of video data center setting up cache cluster and cache resources dispatching method thereof
CN105656853B (en) * 2014-11-14 2018-11-20 华为技术有限公司 A kind of message delivery method and relevant apparatus
CN105516245B (en) * 2015-11-25 2018-12-14 国家计算机网络与信息安全管理中心 A kind of system and implementation method of the load balancing based on stream
CN107231269B (en) * 2016-03-25 2020-04-07 阿里巴巴集团控股有限公司 Accurate cluster speed limiting method and device
CN106487918B (en) * 2016-11-07 2019-06-18 清华大学 A MOOC system based on edX platform
CN108600386A (en) * 2018-05-09 2018-09-28 数据堂(北京)科技股份有限公司 A kind of method and system that data service is provided
CN110378707B (en) * 2019-07-24 2023-04-18 北京慧眼智行科技有限公司 Information processing method and device
CN110740161B (en) * 2019-08-30 2022-05-13 武汉烽火众智数字技术有限责任公司 System and method for adapting converged communication
CN111652798B (en) * 2020-05-26 2023-09-29 浙江大华技术股份有限公司 Face pose migration method and computer storage medium
CN112751761A (en) * 2020-12-28 2021-05-04 中国农业银行股份有限公司 Transaction routing switching method, intermediate system and service processing system
CN113810468B (en) * 2021-08-13 2023-04-18 济南浪潮数据技术有限公司 Method, system, equipment and storage medium for distributing requests by gateway under K8s architecture

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101207550A (en) * 2007-03-16 2008-06-25 中国科学技术大学 Load balancing system and method for realizing load balancing of multiple services

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101207550A (en) * 2007-03-16 2008-06-25 中国科学技术大学 Load balancing system and method for realizing load balancing of multiple services

Also Published As

Publication number Publication date
CN101938502A (en) 2011-01-05

Similar Documents

Publication Publication Date Title
CN101938502B (en) Server cluster system and load balancing method
US11411897B2 (en) Communication method and communication apparatus for message queue telemetry transport
CN110311983B (en) Service request processing method, device and system, electronic equipment and storage medium
KR101887581B1 (en) Flow-based packet transport device and packet management method thereof
JP5741150B2 (en) Relay device, relay program, and relay method
CN101610222A (en) Client-based server selection method and device
CN101296176B (en) Data processing method and apparatus based on cluster
CN101499995B (en) A business scheduling method, system and device for business scheduling
US20150088995A1 (en) Method and apparatus for sharing contents using information of group change in content oriented network environment
CN113361913A (en) Communication service arranging method, device, computer equipment and storage medium
CN113127168A (en) Service distribution method, system, device, server and medium
US20210250416A1 (en) Systems and methods for determining a destination location for transmission of packetized data in a network system based on an application server attribute
US7187683B1 (en) Statistics data collection mechanism for distributed, high-speed data processing environments
CN109981795A (en) Resource request dispatching method and device
US20130318244A1 (en) System and method for assigning server to terminal and efficiently delivering messages to the terminal
CN111600929B (en) Transmission line detection method, routing strategy generation method and proxy server
US20090300182A1 (en) Computer-readable storage medium storing event control program, event control method, and event controller
CN108255853B (en) Plug-in type request asynchronous processing method and system
CN114490100A (en) Message queue telemetry transmission load balancing method and device and server
CN108243170A (en) Data access system and method based on socket frames
JP3685110B2 (en) File transfer system, apparatus, method, and recording medium recording file transfer program
CN112769960B (en) Active flow control method and system based on Nginx server
CN111240867B (en) Information communication system and method
JP2013182349A (en) System, program and method for distributed cache
CN108055305B (en) Storage expansion method and storage expansion device

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C53 Correction of patent for invention or patent application
CB03 Change of inventor or designer information

Inventor after: Cheng Bo

Inventor after: Zhang Yang

Inventor after: Ye Bo

Inventor after: Huang Liting

Inventor after: Chen Junliang

Inventor after: Wang Yue

Inventor after: Liu Xihe

Inventor before: Cheng Bo

Inventor before: Zhang Yang

Inventor before: Ye Bo

Inventor before: Huang Liting

Inventor before: Chen Junliang

Inventor before: Wang Yue

Inventor before: Liu Xihe

C14 Grant of patent or utility model
GR01 Patent grant
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20130327

Termination date: 20140714

EXPY Termination of patent right or utility model