CN102123179A - Load balancing method and system applied to distributed application system - Google Patents
Load balancing method and system applied to distributed application system Download PDFInfo
- Publication number
- CN102123179A CN102123179A CN2011100753854A CN201110075385A CN102123179A CN 102123179 A CN102123179 A CN 102123179A CN 2011100753854 A CN2011100753854 A CN 2011100753854A CN 201110075385 A CN201110075385 A CN 201110075385A CN 102123179 A CN102123179 A CN 102123179A
- Authority
- CN
- China
- Prior art keywords
- server
- load
- client
- request
- module
- 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.)
- Pending
Links
Images
Abstract
This invention relates to a load balancing method and system applied to a distributed application system. The method comprises the steps of: receiving a request sent by a client; judging whether the client establishes a connection with a server, when no connection is established, selecting a server with lighter load to establishing a connection with the client; when the connection is established between the client and the server, judging whether the load of server is excessive; when the load of server is excessive, releasing the connection of the client with the server and re-selecting other servers with lighter load to establish a connection; and submitting the request to the connected server for execution. The invention avoids that the server can continuously process the request of the client under the condition of excessive load of the server, and ensures balance distribution of the load among the servers, thereby improving the reliability of the load balancing. .
Description
Technical field
The present invention relates to areas of information technology, relate to a kind of load-balancing method and system that is applied to distribution application system in particular.
Background technology
At present each core of existing network is along with the raising of traffic carrying capacity, the quick growth of visit capacity and data traffic, and its disposal ability and calculating strength also correspondingly increase, and make single equipment can't bear, so load-balancing mechanism arise at the historic moment at all.
Load balancing is meant in network environment, with load balancing be assigned on many computers, network connector, processor, hardware device or other resource so that obtain higher resource utilization, improve the throughput of system, reduce the response time, thereby avoid load overweight.
The method of existing a kind of load balancing, be have in client pending when professional, directly select the lighter server of load, then with this server on the service object connect, by service object's corresponding business request that client sends of finishing dealing with, and in distribution application system, there is the concurrent operations of a large amount of clients, the server that connects with client may be handled the request of a plurality of COS, system is in running, serious unbalanced phenomena will appear in the load of server, and owing to finish a business, client may need to send a series of request, between the service object in client and the server is to carry out information interaction based on a kind of the connection for a long time, also can cause the load of server overweight, therefore, adopt existing this method, still have the unbalanced phenomenon of server load in the system.
Summary of the invention
In view of this, the invention provides a kind of method and system of realizing load balancing, solved the unbalanced phenomenon of server load in the system.
For achieving the above object, the invention provides following technical scheme:
A kind of load-balancing method that is applied to distribution application system, described method comprises:
A: receive the request that client sends;
B: judge whether described client connects with server, if then enter step D, otherwise enter step C;
C: select the lighter server of load, and set up the connection between described client and the selected server;
D: judge whether the server load that connects with described client is overweight, if, then discharge being connected of client and described server, return step C, otherwise enter step e;
E: described request is sent to the server that connects with described client handles.
Preferably, before the request that described reception client sends, also comprise:
With the server record that started in registration table;
Monitor the server state in the described registration table and be recorded in the registration table, described state comprises the service state and the load condition of server;
Load calculation average load according to the Servers-all in the registration table.
Preferably, describedly judge described server load overweight comprising whether:
Judge described server load whether greater than system's first preset value and described server load with respect to the percentage of described average load whether greater than system's second preset value.
Preferably, the state of the server in the described registration table of described monitoring also is recorded in the registration table, comprising:
The state of the server that the periodicity monitoring has started also is recorded in the registration table;
When monitoring server when unavailable, it is unavailable or delete the record of described server for mark in registration table.
Preferably, described method also comprises:
When receiving the processing request failure information that server returns, discharge being connected of client and described server, return step C.
Preferably, when server does not have load overweight, describedly described request is sent to described server and by also comprising after the described server process request:
When also having the request of client transmission, repeated execution of steps A～step e is until handling all requests.
A kind of SiteServer LBS that is applied to distribution application system, described system comprises client manager module, load balancing module and server management module, wherein:
Described client manager module, be used to receive the request that client sends, judge whether described client connects with server, when client and server connect, described request is sent to server management module, otherwise the starting load balance module is set up being connected of client and described load balancing module selected server; When receiving the overweight information of server load that is connected with client of server management module feedback, discharge the starting load balance module again that is connected also of client and described server;
Load balancing module is used to select the lighter server of load and gives client manager module with described server identification feedback information;
Server management module, be used to receive the request that client manager module sends, judge whether the server load that is connected with described client is overweight, if, then give client manager module, otherwise described request is sent to described server the overweight feedback information of load.
Preferably, described load balancing module also is used for the server that will start and the service state and the load condition of described server is recorded in registration table, and described registration table is the internal storage location in the described load balancing module; Then,
Described server management module also be used to monitor described record server service state and load condition and feed back to load balancing module.
Preferably, described load balancing module also is used for the load calculation average load according to the Servers-all of record, then,
After described server management module specifically is used to receive the described request of client manager module transmission, judge the server load be connected with described client whether greater than system's first preset value and described server load with respect to the percentage of described average load whether greater than system's second preset value, if, then give client manager module, otherwise described request is sent to described server the overweight feedback information of load.
Preferably, described server management module also is used for reception server and handles the request failure information, and gives client manager module with described feedback information; Then,
Described client manager module also is used to receive when handling the request failure information, discharges the starting load balance module again that is connected also of client and described server.
Via above-mentioned technical scheme as can be known, compared with prior art, the present invention openly provides a kind of method and system that is applied to the load balancing of distribution application system, receive the request that client sends by system of the present invention, judge at first whether this client connects, when not connecting, select lighter server and the described client of load to connect, after connecting, client and server judge whether described server load is overweight, when load is overweight, then indicate client to discharge and being connected of described server, reselect other servers, do not have overweight until selecting the server load that connects with client, avoided under the overweight situation of server load, still continuing to handle the request of client, ensured to load on balanced distribution the between the server, thereby improved the reliability of load balancing.
Description of drawings
In order to be illustrated more clearly in the embodiment of the invention or technical scheme of the prior art, to do to introduce simply to the accompanying drawing of required use in embodiment or the description of the Prior Art below, apparently, accompanying drawing in describing below only is embodiments of the invention, for those of ordinary skills, under the prerequisite of not paying creative work, can also obtain other accompanying drawing according to the accompanying drawing that provides.
Fig. 1 is a kind of flow chart that is applied to the load-balancing method embodiment 1 of distribution application system of the present invention;
Fig. 2 is a kind of flow chart that is applied to the load-balancing method embodiment 2 of distribution application system of the present invention;
Fig. 3 is a kind of structure chart that is applied to the SiteServer LBS specific embodiment of distribution application system of the present invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the invention, the technical scheme in the embodiment of the invention is clearly and completely described, obviously, described embodiment only is the present invention's part embodiment, rather than whole embodiment.Based on the embodiment among the present invention, those of ordinary skills belong to the scope of protection of the invention not making the every other embodiment that is obtained under the creative work prerequisite.
The embodiment of the invention discloses a kind of load-balancing method and system that is applied to distribution application system, receive the request that client sends by system of the present invention, judge at first whether this client connects, when not connecting, select lighter server and the described client of load to connect, after connecting, client and server judge whether described server load is overweight, when load is overweight, then indicate client to discharge and being connected of described server, reselect other servers, do not have overweight until selecting the server load that connects with client, avoided under the overweight situation of server load, still continuing to handle the request of client, influence the load balancing of server, thereby improved the reliability of load balancing.
Referring to Fig. 1, show a kind of flow chart that is applied to the load-balancing method specific embodiment 1 of distribution application system of the present invention, can may further comprise the steps:
Step 101: receive the request that client sends.
In distribution application system, need be connected based on network between the two alternately between client and the server, client sends corresponding request then, server receives described request and handles, in the embodiment of the invention, the request of client does not directly send to corresponding server, but earlier through judging whether suitable with client if setting up the server that network is connected, ask processing afterwards again, thereby can realize the load balancing of server.
Step 102: judge whether described client connects with server, if then enter step 104, otherwise enter step 103.
The business operation that client need be finished may comprise a plurality of pending requests, server is after once request is finished dealing with, if client also has other requests pending, then can't disconnect at once and being connected, connect and continue to send other pending requests and be based on this network with the network of described server.
Step 103: select the lighter server of load, and set up being connected of described client and selected server.
After system receives the request of client transmission, when described client does not connect with server, then from server, select a server that load is lighter, setting up client according to the identification information of this server is connected with the network of described server, owing to be to ask to handle by corresponding service object in the server, it specifically can be that this object identifier can service object of only sign according to the service object's who is used to handle respective request in the server object identifier.The networking of setting up the service object in client and the described server is connected.
In the present embodiment, after client sends request, when client during, select the lighter server of load with this client connects by system, and need not to know as client and be and being connected of which concrete server foundation not with the annexation of server.
When server began to start operation, system promptly noted the server that has started, is kept in the registration table, and registration table is the internal storage location in the system.Note the server that has started, can monitor this server, the state of monitor server also is recorded in the registration table, and described state comprises the service state of server, promptly whether is handling request or is withdrawing from and load condition.The load condition of the server that writes down can be that indexs such as the flow, visit capacity by monitor server obtain.System can select lighter server of load and client and go to connect according to the loading condition of record.
Need to prove, when selecting server failure, then send abnormal information, process ends to client.
Step 104: judge whether the server load that connects with described client is overweight, if, then enter step 105, if not, then enter step 106.
The server that connects with client does not disconnect this and is connected after handling once request, and when client connects continuation transmission request based on this, do not consider the actual loading situation of this server, the load of described server may be overweight, it may carry out a plurality of client requests, if still carry out described request, will cause the load of server overweight, thereby make that unbalanced phenomena appears in the load of server in the network system by this server.So need to judge whether the load of the server that connects with client is overweight.
Wherein, the concrete standard of judgement can be: whether the load of judging this server greater than first preset value of system, if greater than first preset value of system, then can enter step 105, if less than first preset value of system, then can enter step 106.
The concrete standard of judging, another preferred scheme can be: by in the step 103 as can be known, system can write down the loading condition of all servers that started, the average load that can calculate Servers-all according to each server load condition of record.Therefore, judge whether overweight being specifically as follows of server load: the load of judging this server with respect to the percentage of average load whether greater than second preset value of system, if, then enter step 105, if not, then enter step 106.
The concrete standard of judging, another preferred scheme can also be: judge this server load whether greater than system's first preset value and described server load with respect to the percentage of average load whether greater than system's second preset value, if, then enter step 105, if not, then enter step 106.
Wherein, first preset value and second preset value are provided with according to practical situations is concrete, for example, in the application of fast Fourier transform, fast fourier transform is a compute-intensive applications, in this is used, cpu as keystone resources by the fast fourier transform task sharing of a plurality of concurrent execution, and the number that limits the task of concurrent execution on the server can not be greater than 4 times of cpu number, and on the server of single cpu, the task number of the concurrent execution of a server is 4 to the maximum.The load of server can represent that at this moment, first preset value is that 1, the second preset value is 100% with the concurrent number of tasks of carrying out on the server.First preset value during this uses is 1, count no more than 2 if represent concurrent the executing the task on this server, even it is unbalanced load to occur, can not influence each task executions on this server yet, therefore not needing to switch other server carries out this task, have only when this server concurrent and execute the task number greater than 2 the time, just need the consideration switching server.Second preset value is 100%, if represent that the duty ratio average load on this server is big, then there is a server at least, task of concurrent execution lacks 1 than the task of concurrent execution on this server on it, therefore, new task should switch on the little server of concurrent number of tasks and carry out.
And for example, in the application of ticket-booking service, the ticket booking business is typical online transaction services, the amount of calculation of its single business is also little, and the response time is also very fast, and what the ticket booking business mainly faced is the professional concurrent executive problem of extensive ticket booking, if professional concurrency is not high, then a plurality of business are carried out the not significantly influence for the user on a server, but after concurrency surpasses certain limit, the performance of server will sharply descend.Server in the at present common personal computer can effectively be supported the concurrent execution of 100 business substantially, therefore, and the concurrency of seat reservation system meeting limit service, when professional number during greater than this concurrency, the business that surpasses will enter waiting list, wait for that other business executes, and carry out again.In this is used, the load of server can be represented with the professional number on the server (carrying out and be in the professional number of wait state), for common server, first preset value is 100, if the voice and packet data concurrent service number on the expression server does not surpass 100, then do not need to redistribute server, second preset value can be set to 105%, if represent that the professional number on this server is more than the average traffic number on each server, just need new service dispatching is carried out to the lighter server of load.
Need to prove, more than cited example be in the actual scene two concrete application, be not as concrete qualification to first preset value and second preset value, those skilled in the art are scrutable to be, first preset value and second preset value are according to different applicable cases and difference is given unnecessary details no longer one by one at this.
Step 105: the release client is connected with described server, returns step 103.
Under the overweight situation of server load, then this server is not carried out the request of client, then be connected with the network of described server, return step 103 again, from the server of record, search the lighter server of another load and return to client for client disconnects.
Step 106: described request is sent to the server that connects with described client, handles by described server.
When the load of server does not have when overweight, then can ask to handle by the respective service object in this server, comprised the particular content of carrying out this requested service type and request in the request that client sends, server can select suitable service object to ask to handle, and the result that will handle returns to client.
If client also has other pending requests, the then described operation of repeated execution of steps 101～step 106 is until handling all requests.
Need to prove that if server process request failure, the processing failure information that returns of reception server then discharges being connected of client and this server, returns step 103 and continues execution.
In embodiments of the present invention, after receiving the request of client transmission, when client connects with server, judge directly then whether this server load is overweight, not setting up network with server when client is connected, then select lighter server of load and described client to connect, judge again afterwards whether the server load that links to each other with described client is overweight, when overweight, do not indicate described server to carry out described request, rejudge but reselect other servers, do not have overweight until selecting the server load that connects with client, avoided under the overweight situation of server load, still continuing to handle the request of client, influence the load balancing of server, thereby improved the reliability of load balancing, and server is then reselected other servers after handling the request failure, the process of selecting is identical with above-mentioned explanation, thereby has improved the accuracy of the request of handling.
Referring to Fig. 2, show a kind of flow chart that is applied to the load-balancing method embodiment 2 of distribution application system of the present invention, can may further comprise the steps:
Step 201: the state of the server in the described registration table is monitored and write down to the server record that will start in registration table.
When server begins to start operation, system promptly notes the server that has started, be kept in the registration table, registration table is the internal storage location in the system, and the state of the server that has write down in the monitoring registration table, the service state and the load condition that comprise server, and with state recording in registration table.
Wherein, monitoring to server is carried out always, preferably, can periodically carry out the status monitoring of state server, the concrete cycle can be set according to actual conditions, server is unavailable when monitoring, and perhaps withdraws from, then this service object of deletion from registration table, server can be used and move normal, then note the load of this server, if the service state of server is uncertain, then mark its be unavailable.
Step 202: according to the load calculation average load of the Servers-all in the registration table.
According to the loading condition of the server that writes down, calculate average load.
Step 203: receive the request that client sends.
Step 204: judge whether described client connects with server, if then enter step 206.If not, then enter step 205.
Step 205: select the lighter server of load, and set up being connected of client and selected server.
Select the server feedback that service state is normal and load is the lightest in the record from registration table and give client, set up client and be connected with the network of selected server.
If feedback occurs unusual, for example, server is all unavailable or when having withdrawed from, and then sends unexpected message, process ends to client.
Step 206: judge described server load whether greater than system's first preset value and described server load with respect to the percentage of described average load whether greater than system's second preset value, if, then enter step 207, if not, then enter step 208.
Wherein, system's first preset value and system's second preset value set in advance according to practical situations.
When the load of server during greater than system's second preset value, think that then this server load is overweight, otherwise it is overweight to think that server load does not have with respect to the percentage of average load greater than the load of system's first preset value and server.
Step 207: the release client is connected with described server, returns step 205.
When load is overweight, promptly discharges and be connected, return step 205 again, from the server that writes down, reselect the lighter server of load, so that rebulid connection for client with the network of described server.
Step 208: described request is sent to described server, and receives the result who returns after the described server process request.
Step 209: judge according to the result who returns whether server handles success, if, then enter step 210, if not, return step 207.
Server asks to handle, and when handling failure, then will handle the request failure information and return to system, when receiving this processing request failure information, then reselects server, runs succeeded to guarantee request.
Step 210: when also having the request of client transmission, return step 204.
After executing a request, can judge whether other pending requests in addition,, then continue to receive the request that described client sends, return step 204,, finish whole flow process until handling all requests when client also has other pending requests.If when not having other requests, direct process ends.
In embodiments of the present invention, the server that has started is monitored, so that select the lighter server of load and client connects, after connecting with client, whether load is overweight judging this server, when load is overweight, then from the record of registration table, selects the lighter server of other loads again, and then this server is sent in request handled.Avoided under the overweight situation of server load, still continuing to handle the request of client, influence the load balancing of server, thereby improved the reliability of load balancing, and server is after handling the request failure, then reselect other servers, the success rate that the request that guaranteed is carried out.
Referring to Fig. 3, show a kind of structure chart that is applied to the SiteServer LBS specific embodiment of distribution application system of the present invention, described system comprises client manager module 301, load balancing module 302 and server management module 303,
Described client manager module 301: be used to receive the request that client sends, judge whether described client connects with server, when client and server connect, described request is sent to server management module, otherwise starting load balance module 302 is set up being connected of client and the selected server of described load balancing module; When receiving the overweight information of server load that is connected with client of server management module 303 feedback, discharge the starting load balance module 302 again that is connected also of client and described server.
Described load balancing module 302: be used to select the lighter server of load and give client manager module 301 with described server identification feedback information.
Described server management module 303: after being used to receive the described request of client manager module 301 transmissions, judge whether the server load that is connected with described client is overweight, if, then give client manager module 301 with the overweight feedback information of load, if not, then described request is sent to described server.
In the SiteServer LBS provided by the present invention, described client manager module 301 can be in the process with client, is in charge of being connected between client and the server, the request message that administrative client sends; Described server management module 303 can be in the process with server side, is responsible for the loading condition of monitor server, and when server load was overweight, indication server refusal was carried out described request; Described load balancing module 302, can be independently a process or an equipment, when receiving the information of client manager module 301 request distribution servers, select the lighter server feedback of load to give client manager module 301, so that client manager module 301 is set up being connected of client and selected server.
Wherein, described load balancing module 302 also is used for the server that will start and the service state and the load condition of described server is recorded in registration table, calculates average load according to the loading condition of the server of record, and registration table is the internal storage location in the load balancing module, then
Described server management module 303 also be used for monitoring described registration table server service state and load condition and feed back to load balancing module 302.
Wherein, after described server management module 303 specifically is used to receive the described request of client manager module 302 transmissions, judge server load that described client connects whether greater than system's first preset value if, confirm that then load is overweight, give client manager module with the overweight feedback information of load, if not, then described request being sent to this server handles.Perhaps,
After being used to receive the described request of client manager module 302 transmissions, judge the server load be connected with described client with respect to the percentage of described average load whether greater than system's second preset value, if, confirm that then load is overweight, give client manager module with the overweight feedback information of load, if not, then described request being sent to this server handles.Perhaps,
After being used to receive the described request of client manager module 302 transmissions, judge the server load be connected with described client whether greater than system's first preset value and described server load with respect to the percentage of described average load whether greater than system's second preset value, if, confirm that then load is overweight, give client manager module with the overweight feedback information of load, if not, then described request being sent to this server handles.
Wherein, described server management module 303 also is used for reception server and handles the request failure information, and gives client manager module 301 with described feedback information, then,
Described client manager module also is used to receive when handling the request failure information, discharges the starting load balance module 302 again that is connected also of client and described server.
Based on SiteServer LBS provided by the invention, the method for load balancing can be described below:
When server management module monitors startup of server, the server info that starts is fed back to load balancing module, be recorded in the registration table by load balancing module, and to the request of server management module transmission load monitoring, the indication server management module is carried out status monitoring to the server that writes down in the registration table, server management module is feeding back to load balancing module with monitoring result, is recorded in registration table and is gone out average load according to the load calculation of Servers-all by load balancing module.
When client manager module receives client requests, judge at first whether this client connects with corresponding server, if no, then indicate load balancing module to select the server that load is lighter, so that set up being connected of client and selected server; If connect, send described request to server management module, after server management module receives this request, at first whether the load of this requested service device of judgment processing is overweight, if it is overweight, then give client manager module with overweight feedback information, the release of client manager module indication client is connected with described server, indicates load balancing module to select the server that load is lighter again; If do not have overweightly, then described request is sent to server, so that the server process described request.
Server management module feeds back to client manager module with the result of server, if request is handled successfully, then the result is returned to client, if failure, then client manager module discharges being connected of client and this server, indicates server that load is lighter of load balancing module selection again.
In embodiments of the present invention, after client manager module receives the request of client transmission, select the lighter server feedback of load by load balancing module and give client, so that client connects, judge by server management module whether the server load that is connected with client is overweight then, when overweight, reselect server by load balancing module, do not have when overweight, then by server management module this server being sent in request handles, by system provided by the invention, avoided under the overweight situation of server load, still continuing to handle the request of client, influence the load balancing of server in the system, thereby improved the reliability of load balancing.
System embodiment described above only is schematic, wherein said unit as the separating component explanation can or can not be physically to separate also, the parts that show as the unit can be or can not be physical locations also, promptly can be positioned at a place, perhaps also can be distributed on a plurality of network element.Can select wherein some or all of module to realize the purpose of present embodiment scheme according to the actual needs.Those of ordinary skills promptly can understand and implement under the situation of not paying creative work.
Each embodiment adopts the mode of going forward one by one to describe in this specification, and what each embodiment stressed all is and the difference of other embodiment that identical similar part is mutually referring to getting final product between each embodiment.For the disclosed device of embodiment, because it is corresponding with the embodiment disclosed method, so description is fairly simple, relevant part partly illustrates referring to method and gets final product.
At last, also need to prove, in this article, relational terms such as first and second grades only is used for an entity or operation are made a distinction with another entity or operation, and not necessarily requires or hint and have the relation of any this reality or in proper order between these entities or the operation.And, term " comprises ", " comprising " or its any other variant are intended to contain comprising of nonexcludability, thereby make and comprise that process, method, article or the equipment of a series of key elements not only comprise those key elements, but also comprise other key elements of clearly not listing, or also be included as this process, method, article or equipment intrinsic key element.Do not having under the situation of more restrictions, the key element that limits by statement " comprising ... ", and be not precluded within process, method, article or the equipment that comprises described key element and also have other identical element.
To the above-mentioned explanation of the disclosed embodiments, make this area professional and technical personnel can realize or use the present invention.Multiple modification to these embodiment will be conspicuous concerning those skilled in the art, and defined herein General Principle can realize under the situation that does not break away from the spirit or scope of the present invention in other embodiments.Therefore, the present invention will can not be restricted to these embodiment shown in this article, but will meet and principle disclosed herein and features of novelty the wideest corresponding to scope.
Claims (10)
1. a load-balancing method that is applied to distribution application system is characterized in that, described method comprises:
A: receive the request that client sends;
B: judge whether described client connects with server, if then enter step D, otherwise enter step C;
C: select the lighter server of load, and set up the connection between described client and the selected server;
D: judge whether the server load that connects with described client is overweight, if, then discharge being connected of client and described server, return step C, otherwise enter step e;
E: described request is sent to the server that connects with described client handles.
2. method according to claim 1 is characterized in that, before the request that described reception client sends, also comprises:
With the server record that started in registration table;
Monitor the server state in the described registration table and be recorded in the registration table, described state comprises the service state and the load condition of server;
Load calculation average load according to the Servers-all in the registration table.
3. method according to claim 2 is characterized in that, describedly judges described server load overweight comprising whether:
Judge described server load whether greater than system's first preset value and described server load with respect to the percentage of described average load whether greater than system's second preset value.
4. method according to claim 2 is characterized in that, the state of the server in the described registration table of described monitoring also is recorded in the registration table, comprising:
The state of the server that the periodicity monitoring has started also is recorded in the registration table;
When monitoring server when unavailable, it is unavailable or delete the record of described server for mark in registration table.
5. method according to claim 1 is characterized in that, described method also comprises:
When receiving the processing request failure information that server returns, discharge being connected of client and described server, return step C.
6. method according to claim 1 is characterized in that, when server does not have load overweight, describedly described request is sent to described server and by also comprising after the described server process request:
When also having the request of client transmission, repeated execution of steps A～step e is until handling all requests.
7. a SiteServer LBS that is applied to distribution application system is characterized in that, described system comprises client manager module, load balancing module and server management module, wherein:
Described client manager module, be used to receive the request that client sends, judge whether described client connects with server, when client and server connect, described request is sent to server management module, otherwise the starting load balance module is set up being connected of client and described load balancing module selected server; When receiving the overweight information of server load that is connected with client of server management module feedback, discharge the starting load balance module again that is connected also of client and described server;
Load balancing module is used to select the lighter server of load and gives client manager module with described server identification feedback information;
Server management module, be used to receive the request that client manager module sends, judge whether the server load that is connected with described client is overweight, if, then give client manager module, otherwise described request is sent to described server the overweight feedback information of load.
8. system according to claim 7, it is characterized in that, described load balancing module also is used for the server that will start and the service state and the load condition of described server is recorded in registration table, and described registration table is the internal storage location in the described load balancing module; Then,
Described server management module also be used to monitor described record server service state and load condition and feed back to load balancing module.
9. system according to claim 8 is characterized in that, described load balancing module also is used for the load calculation average load according to the Servers-all of record, then,
After described server management module specifically is used to receive the described request of client manager module transmission, judge the server load be connected with described client whether greater than system's first preset value and described server load with respect to the percentage of described average load whether greater than system's second preset value, if, then give client manager module, otherwise described request is sent to described server the overweight feedback information of load.
10. system according to claim 7 is characterized in that, described server management module also is used for reception server and handles the request failure information, and gives client manager module with described feedback information; Then,
Described client manager module also is used to receive when handling the request failure information, discharges the starting load balance module again that is connected also of client and described server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011100753854A CN102123179A (en) | 2011-03-28 | 2011-03-28 | Load balancing method and system applied to distributed application system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011100753854A CN102123179A (en) | 2011-03-28 | 2011-03-28 | Load balancing method and system applied to distributed application system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102123179A true CN102123179A (en) | 2011-07-13 |
Family
ID=44251629
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2011100753854A Pending CN102123179A (en) | 2011-03-28 | 2011-03-28 | Load balancing method and system applied to distributed application system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102123179A (en) |
Cited By (29)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102281329A (en) * | 2011-08-02 | 2011-12-14 | 北京邮电大学 | Resource scheduling method and system for platform as a service (Paas) cloud platform |
| CN102801726A (en) * | 2012-08-06 | 2012-11-28 | 上海西本网络科技有限公司 | Communication system and communication method between client and server side |
| CN102821154A (en) * | 2012-08-13 | 2012-12-12 | 苏州阔地网络科技有限公司 | Multifunctional instance communication method and system |
| CN102843427A (en) * | 2012-08-13 | 2012-12-26 | 苏州阔地网络科技有限公司 | Multi-instance communication method and system |
| CN102843365A (en) * | 2012-08-13 | 2012-12-26 | 苏州阔地网络科技有限公司 | Single-process multi-instance communication method and system |
| CN102902828A (en) * | 2012-11-16 | 2013-01-30 | 北京奇虎科技有限公司 | Method and device for retrieval |
| CN103746963A (en) * | 2013-12-16 | 2014-04-23 | 深圳百科信息技术有限公司 | SIP server cluster system and service application request processing method thereof |
| CN104009933A (en) * | 2014-05-22 | 2014-08-27 | 北京金山网络科技有限公司 | Cluster service load balancing method and system, central server and standby node server |
| CN104125271A (en) * | 2014-07-07 | 2014-10-29 | 四川中电启明星信息技术有限公司 | Distributed architecture method applied to visual data pushing platform |
| CN104935664A (en) * | 2015-06-19 | 2015-09-23 | 中国铁道科学研究院电子计算技术研究所 | Seat automatic load balancing method and system |
| CN105007181A (en) * | 2015-07-07 | 2015-10-28 | 广州日滨科技发展有限公司 | Elevator Internet of Things (IoT) communication scheduling method and system |
| CN105099935A (en) * | 2015-07-28 | 2015-11-25 | 小米科技有限责任公司 | Server load control method and device |
| CN105262714A (en) * | 2014-06-27 | 2016-01-20 | 中兴通讯股份有限公司 | Method and device for dynamically reporting call tickets in network communication system |
| CN105591964A (en) * | 2015-10-14 | 2016-05-18 | 中国银联股份有限公司 | Device and method for overload protection for Internet system |
| CN106572181A (en) * | 2016-11-08 | 2017-04-19 | 深圳市中博睿存科技有限公司 | Object storage interface load balancing method and system based on cluster file system |
| CN106604269A (en) * | 2016-11-30 | 2017-04-26 | 努比亚技术有限公司 | Mobile terminal network communication method and system |
| CN103618738B (en) * | 2013-12-09 | 2017-05-03 | 惠州华阳通用电子有限公司 | Intelligent load distribution system and method for achieving TCP long connection and communication |
| CN106657212A (en) * | 2016-09-07 | 2017-05-10 | 深圳怡化电脑股份有限公司 | Self-service terminal state monitoring method and system |
| CN103746839B (en) * | 2013-12-27 | 2017-06-16 | 新浪网技术(中国)有限公司 | PaaS systems and PaaS are using the VM node scheduling methods in pond |
| CN106934031A (en) * | 2017-03-14 | 2017-07-07 | 中国银行股份有限公司 | The monitoring of focus record and processing method and processing device in real time processing system |
| CN107809342A (en) * | 2017-12-13 | 2018-03-16 | 深圳市智物联网络有限公司 | A kind of load-balancing method and load balancing apparatus |
| CN108055338A (en) * | 2017-12-22 | 2018-05-18 | 创新科存储技术有限公司 | A kind of ISCSI accesses load-balancing method |
| CN109347984A (en) * | 2018-12-03 | 2019-02-15 | 河南省四通锅炉有限公司 | A kind of boiler monitoring method and device based on Internet of Things for intelligent chemical plant |
| CN110012044A (en) * | 2018-01-04 | 2019-07-12 | 财团法人工业技术研究院 | Dynamic duty transfer method and server |
| CN110178352A (en) * | 2016-12-13 | 2019-08-27 | Abb瑞士股份有限公司 | Client is had connected using refusal with the multi-client of the routine of balance system/multiserver administration method and system |
| CN110178351A (en) * | 2016-12-13 | 2019-08-27 | Abb瑞士股份有限公司 | Multi-client/multiserver administration method and system |
| CN111131505A (en) * | 2019-12-31 | 2020-05-08 | 深圳市网心科技有限公司 | Data transmission method, equipment, system, device and medium based on P2P network |
| CN111522650A (en) * | 2019-02-02 | 2020-08-11 | 阿里巴巴集团控股有限公司 | Service request processing method and device of distributed system and electronic equipment |
| CN117061525A (en) * | 2023-10-11 | 2023-11-14 | 江西云眼视界科技股份有限公司 | Camera access method, system, computer and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101009648A (en) * | 2006-12-27 | 2007-08-01 | 北京航空航天大学 | Multi-server hierarchical alterative load balance method |
| CN101127632A (en) * | 2006-08-15 | 2008-02-20 | 腾讯科技（深圳）有限公司 | A method, system and redirector for server traffic control |
| CN101834877A (en) * | 2010-06-03 | 2010-09-15 | 华中科技大学 | Method and system for balancing dynamic load based on distributed SIP architecture |
| CN101854299A (en) * | 2010-05-21 | 2010-10-06 | 中国科学院软件研究所 | Dynamic load balancing method of release/subscription system |
-
2011
- 2011-03-28 CN CN2011100753854A patent/CN102123179A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101127632A (en) * | 2006-08-15 | 2008-02-20 | 腾讯科技（深圳）有限公司 | A method, system and redirector for server traffic control |
| CN101009648A (en) * | 2006-12-27 | 2007-08-01 | 北京航空航天大学 | Multi-server hierarchical alterative load balance method |
| CN101854299A (en) * | 2010-05-21 | 2010-10-06 | 中国科学院软件研究所 | Dynamic load balancing method of release/subscription system |
| CN101834877A (en) * | 2010-06-03 | 2010-09-15 | 华中科技大学 | Method and system for balancing dynamic load based on distributed SIP architecture |
Cited By (45)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102281329B (en) * | 2011-08-02 | 2013-11-20 | 北京邮电大学 | Resource scheduling method and system for platform as a service (Paas) cloud platform |
| CN102281329A (en) * | 2011-08-02 | 2011-12-14 | 北京邮电大学 | Resource scheduling method and system for platform as a service (Paas) cloud platform |
| CN102801726A (en) * | 2012-08-06 | 2012-11-28 | 上海西本网络科技有限公司 | Communication system and communication method between client and server side |
| CN102801726B (en) * | 2012-08-06 | 2016-03-30 | 上海西本网络科技有限公司 | Communication system and the communication means between client and service end |
| CN102843365B (en) * | 2012-08-13 | 2015-09-30 | 阔地教育科技有限公司 | A kind of one process many instance communications method and system |
| CN102821154A (en) * | 2012-08-13 | 2012-12-12 | 苏州阔地网络科技有限公司 | Multifunctional instance communication method and system |
| CN102843427A (en) * | 2012-08-13 | 2012-12-26 | 苏州阔地网络科技有限公司 | Multi-instance communication method and system |
| CN102843365A (en) * | 2012-08-13 | 2012-12-26 | 苏州阔地网络科技有限公司 | Single-process multi-instance communication method and system |
| CN102902828A (en) * | 2012-11-16 | 2013-01-30 | 北京奇虎科技有限公司 | Method and device for retrieval |
| CN102902828B (en) * | 2012-11-16 | 2016-04-20 | 北京奇虎科技有限公司 | A kind of method and apparatus for retrieving |
| CN103618738B (en) * | 2013-12-09 | 2017-05-03 | 惠州华阳通用电子有限公司 | Intelligent load distribution system and method for achieving TCP long connection and communication |
| CN103746963B (en) * | 2013-12-16 | 2017-02-15 | 深圳百科信息技术有限公司 | SIP server cluster system and service application request processing method thereof |
| CN103746963A (en) * | 2013-12-16 | 2014-04-23 | 深圳百科信息技术有限公司 | SIP server cluster system and service application request processing method thereof |
| CN103746839B (en) * | 2013-12-27 | 2017-06-16 | 新浪网技术(中国)有限公司 | PaaS systems and PaaS are using the VM node scheduling methods in pond |
| CN104009933A (en) * | 2014-05-22 | 2014-08-27 | 北京金山网络科技有限公司 | Cluster service load balancing method and system, central server and standby node server |
| CN104009933B (en) * | 2014-05-22 | 2018-04-27 | 北京猎豹网络科技有限公司 | A kind of method of cluster service load balancing, system, central server and standby node server |
| CN105262714A (en) * | 2014-06-27 | 2016-01-20 | 中兴通讯股份有限公司 | Method and device for dynamically reporting call tickets in network communication system |
| CN104125271A (en) * | 2014-07-07 | 2014-10-29 | 四川中电启明星信息技术有限公司 | Distributed architecture method applied to visual data pushing platform |
| CN104125271B (en) * | 2014-07-07 | 2018-07-17 | 四川中电启明星信息技术有限公司 | A kind of distributed structure/architecture method being applied to visualization data-pushing platform |
| CN104935664A (en) * | 2015-06-19 | 2015-09-23 | 中国铁道科学研究院电子计算技术研究所 | Seat automatic load balancing method and system |
| CN104935664B (en) * | 2015-06-19 | 2018-12-21 | 中国铁道科学研究院集团有限公司电子计算技术研究所 | Seat automatic load balancing method and system |
| CN105007181A (en) * | 2015-07-07 | 2015-10-28 | 广州日滨科技发展有限公司 | Elevator Internet of Things (IoT) communication scheduling method and system |
| CN105007181B (en) * | 2015-07-07 | 2018-05-08 | 日立楼宇技术（广州）有限公司 | Elevator Internet of Things client/server adaptation scheme and system |
| CN105099935A (en) * | 2015-07-28 | 2015-11-25 | 小米科技有限责任公司 | Server load control method and device |
| CN105591964B (en) * | 2015-10-14 | 2019-08-13 | 中国银联股份有限公司 | A kind of overload protection arrangement and method for internet system |
| CN105591964A (en) * | 2015-10-14 | 2016-05-18 | 中国银联股份有限公司 | Device and method for overload protection for Internet system |
| CN106657212B (en) * | 2016-09-07 | 2020-05-15 | 深圳怡化电脑股份有限公司 | Self-service terminal state monitoring method and system |
| CN106657212A (en) * | 2016-09-07 | 2017-05-10 | 深圳怡化电脑股份有限公司 | Self-service terminal state monitoring method and system |
| CN106572181A (en) * | 2016-11-08 | 2017-04-19 | 深圳市中博睿存科技有限公司 | Object storage interface load balancing method and system based on cluster file system |
| CN106604269A (en) * | 2016-11-30 | 2017-04-26 | 努比亚技术有限公司 | Mobile terminal network communication method and system |
| CN110178351A (en) * | 2016-12-13 | 2019-08-27 | Abb瑞士股份有限公司 | Multi-client/multiserver administration method and system |
| CN110178352A (en) * | 2016-12-13 | 2019-08-27 | Abb瑞士股份有限公司 | Client is had connected using refusal with the multi-client of the routine of balance system/multiserver administration method and system |
| CN106934031A (en) * | 2017-03-14 | 2017-07-07 | 中国银行股份有限公司 | The monitoring of focus record and processing method and processing device in real time processing system |
| CN106934031B (en) * | 2017-03-14 | 2020-03-13 | 中国银行股份有限公司 | Method and device for monitoring and processing hotspot records in real-time processing system |
| CN107809342A (en) * | 2017-12-13 | 2018-03-16 | 深圳市智物联网络有限公司 | A kind of load-balancing method and load balancing apparatus |
| CN108055338B (en) * | 2017-12-22 | 2021-04-09 | 创新科技术有限公司 | ISCSI access load balancing method |
| CN108055338A (en) * | 2017-12-22 | 2018-05-18 | 创新科存储技术有限公司 | A kind of ISCSI accesses load-balancing method |
| CN110012044A (en) * | 2018-01-04 | 2019-07-12 | 财团法人工业技术研究院 | Dynamic duty transfer method and server |
| CN110012044B (en) * | 2018-01-04 | 2022-01-14 | 财团法人工业技术研究院 | Dynamic work transfer method and server |
| CN109347984A (en) * | 2018-12-03 | 2019-02-15 | 河南省四通锅炉有限公司 | A kind of boiler monitoring method and device based on Internet of Things for intelligent chemical plant |
| CN109347984B (en) * | 2018-12-03 | 2021-05-04 | 河南省四通锅炉有限公司 | Boiler monitoring method and device based on Internet of things for intelligent factory |
| CN111522650A (en) * | 2019-02-02 | 2020-08-11 | 阿里巴巴集团控股有限公司 | Service request processing method and device of distributed system and electronic equipment |
| CN111131505A (en) * | 2019-12-31 | 2020-05-08 | 深圳市网心科技有限公司 | Data transmission method, equipment, system, device and medium based on P2P network |
| WO2021134928A1 (en) * | 2019-12-31 | 2021-07-08 | 深圳市网心科技有限公司 | Method, device, system and apparatus for p2p network-based data transmission, and medium |
| CN117061525A (en) * | 2023-10-11 | 2023-11-14 | 江西云眼视界科技股份有限公司 | Camera access method, system, computer and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102123179A (en) | Load balancing method and system applied to distributed application system | |
| CN102143075B (en) | Method and system for achieving load balance | |
| AU689925B2 (en) | Computer system having client-server architecture | |
| CN105956138B (en) | The control method and device of database connection | |
| CN104539713B (en) | service request processing method and device | |
| JP2000172657A (en) | System and method for distributed processing, computer- readable recording medium with program for computer to execute the same method recorded therein, server device and client device | |
| CN103516759B (en) | Cloud system method for managing resource, cloud call center are attended a banquet management method and cloud system | |
| CN102970379A (en) | Method for realizing load balance among multiple servers | |
| CN109785042A (en) | Abnormality eliminating method, server, storage medium and the device of distributed deployment | |
| CN107343112A (en) | Intelligent traffic distribution method based on the layering of call center's seat | |
| US20120233313A1 (en) | Shared scaling server system | |
| CN106131227A (en) | Balancing method of loads, meta data server system and load balance system | |
| CN110474917A (en) | The upper and lower line method of message-oriented middleware, device, equipment and readable storage medium storing program for executing | |
| CN101345770A (en) | Load equalization implementing method, storage control equipment and memory system | |
| CN104268007A (en) | Distributed event request scheduling method and system | |
| EP1816565B1 (en) | Computer system and information processing method | |
| CN108737543B (en) | Distributed Internet of things middleware and working method | |
| EP1867081B1 (en) | Distributed redundancy capacity licensing in a telecommunication network element | |
| CN110225088A (en) | A kind of cloud desktop management method and system | |
| JP3715071B2 (en) | Communication line control system | |
| CN105554126A (en) | Method for realizing distributed deployment of multiple data centers through CDN acceleration mechanism | |
| CN117032987A (en) | Distributed task scheduling method, system, equipment and computer readable medium | |
| CN111835809B (en) | Work order message distribution method, work order message distribution device, server and storage medium | |
| CN115378962B (en) | High-availability communication method and system for storage cluster based on iSCSI protocol | |
| CN104618492B (en) | A kind of data handling system based on multiple servers |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20110713 |