System and method for server selection using competitive evaluation

• US 9,407,721 B2
• Filed: 10/16/2013
• Issued: 08/02/2016
• Est. Priority Date: 10/16/2013
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Svoboda, Rostislav, Slavek, Pavel, Eli, Filip
• Primary Examiner(s): Lin, Wen-Tai
• Application Number:
  US14/055,146
• Publication Number:
  US 20150106422A1
• Time in Patent Office: 1,021 Days
• US Class Current: 1/1
• CPC Class Codes: H04L 67/1004 Server selection for load balancing
• CPC Class Codes: H04L 67/1025 Dynamic adaptation of the criteria on which the server selection is based
• CPC Class Codes: H04L 67/60 Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70

Abstract

A system and method of server selection using competitive evaluation includes receiving a service request at an arbiter running on a computing device, determining whether the service request is associated with a preferred server, and forwarding the service request to the preferred server when the service request is associated with the preferred server. When the service request is not associated with the preferred server, the method further includes using the arbiter to coordinate a competitive evaluation among a plurality of active servers, selecting as the preferred server a first one of the active servers that completes processing of the service request first, and associating the preferred server with the service request. The method further includes receiving a response to the service request from the preferred server and returning the response to a client. The service request is received from the client.

Claims

1. A method of processing a service request, the method comprising:

receiving the service request at an arbiter running on a computing device, the service request being received from a client;

determining whether the service request is associated with a preferred server;

when the service request is not associated with the preferred server;

using the arbiter to coordinate a competitive evaluation among a plurality of active servers by sending the service request in parallel to each of the plurality of active servers;

selecting as the preferred server a first one of the active servers that completes processing of the service request before the others;

preventing others of the active servers other than the first one of the active servers from completing processing of the service request;

associating the preferred server with the service request;

receiving a response to the service request from the preferred server; and

returning the response to the client.

2. The method of claim 1 wherein determining whether the service request is associated with the preferred server comprises searching for a preferred server record matching one or more characteristics of the service request.

3. The method of claim 2 wherein the one or more characteristics are each selected from a group consisting of a client identifier associated with the client and a service identifier associated with a service requested in the service request.

4. The method of claim 2 wherein determining whether the service request is associated with the preferred server further comprises determining whether the preferred server record is expired.

5. The method of claim 4 wherein determining whether the preferred server record is expired comprises determining that the preferred server record is expired when a current time is after an expiration time associated with the preferred server record.

6. The method of claim 5 wherein the expiration time is stored in a valid until field of the preferred server record.

7. The method of claim 5 wherein the expiration time is between one and sixty minutes after a time of a last competitive evaluation that selected the preferred server.

8. The method of claim 4 wherein determining whether the preferred server record is expired comprises determining that the preferred server record is expired when a number of times the preferred server record has been used to determine the preferred server exceeds a threshold.

9. The method of claim 8 wherein the threshold is selected from a range from 10 to 200.

10. The method of claim 1 wherein associating the preferred server with the service request comprises saving a preferred server record in a data structure or a database.

11. The method of claim 1 wherein using the arbiter to coordinate the competitive evaluation among the plurality of active servers comprises:

sending initialization instructions to an application server or a transaction processor associated with each of the active servers so that the arbiter is notified of rollback operations and commit operations initiated on the active servers;

forwarding the service request to each of the active servers; and

waiting for a first notification that the first one of the active servers has initiated a first rollback operation or a first commit operation;

wherein the first notification is received prior to any second notification that any other of the active servers has initiated a respective second rollback operation or a respective second commit operation.

12. The method of claim 11 wherein using the arbiter to coordinate the competitive evaluation among the plurality of active servers further comprises confirming, by the arbiter, that the first rollback operation or the first commit operation is allowed to complete.

13. The method of claim 12 wherein using the arbiter to coordinate the competitive evaluation among the plurality of active servers further comprises returning, by the arbiter, an instruction that each of the other of the active servers perform a rollback when each respective second notification is received.

14. The method of claim 1, further comprising updating a request count in a preferred server record associated with the service request when the service request is associated with the preferred server.

15. A system for processing service requests, the system comprising:

a computing device comprising one or more processors coupled to memory; and

an arbiter stored in the memory and executed by the one or more processors;

wherein the computing device is configured to communicate with a client and a plurality of active servers;

wherein the arbiter is configured to;

receive a service request from the client;

determine whether the service request is associated with a preferred server;

forward the service request to the preferred server when the service request is associated with the preferred server;

when the service request is not associated with the preferred server;

coordinate a competitive evaluation among the plurality of active servers by sending the service request in parallel to each of the plurality of active servers;

select as the preferred server a first one of the active servers that completes processing of the service request before the others;

prevent others of the active servers other than the first one of the active servers from completing processing of the service request;

and

associate the preferred server with the service request;

receive a response to the service request from the preferred server; and

return the response to the client.

16. The system of claim 15 wherein:

the arbiter is further configured to;

send initialization instructions to an application server or a transaction processor associated with each of the active servers so that the arbiter is notified of rollback operations and commit operations initiated on the active servers;

forward the service request to each of the active servers; and

wait for a first notification that the first one of the active servers has initiated a first rollback operation or a first commit operation; and

wherein the first notification is received prior to any second notification that any other of the active servers has initiated a respective second rollback operation or a respective second commit operation.

17. The system of claim 16 wherein the arbiter is further configured to:

confirm that the first rollback operation or the first commit operation is allowed to complete; and

return an instruction that each of the other of the active servers perform a rollback when each respective second notification is received.

18. A non-transitory machine-readable medium comprising a first plurality of machine-readable instructions which when executed by one or more processors associated with an arbiter are adapted to cause the one or more processors to perform a method comprising:

receiving a first request from a client;

determining whether the first request is associated with a first server by matching one or more properties of the first request to a corresponding one or more fields of a server record associated with the first server;

when the first request is not associated with the first server;

using the arbiter to coordinate a competitive evaluation among a plurality of second servers by sending the first request in parallel to each of the plurality of second servers;

selecting as the first server a first one of the second servers that completes handling of the first request before any other of the second servers;

preventing others of the second servers other than the first server from completing processing of the first request;

associating the first server with the first request;

receiving a response to the first request from the first server; and

returning the response to the client.

19. The non-transitory machine-readable medium of claim 18, further comprising a second plurality of machine-readable instructions which when executed by the one or more processors are adapted to cause the one or more processors to perform a method comprising:

sending setup instructions to an application server or a transaction manager associated with each of the second servers so that the arbiter is notified of any transaction ending requests made on the second servers;

forwarding the first request to each of the second servers;

waiting for a first notification that the first one of the second servers has made a first transaction ending request; and

recording the first server in a server field of the server record;

wherein the first notification is received prior to any second notification that any other of the second servers has made a respective second transaction ending request;

wherein the first transaction ending request and the second transaction ending request are each selected from a group consisting of a rollback request and a commit request.

20. The non-transitory machine-readable medium of claim 19, further comprising a third plurality of machine-readable instructions which when executed by the one or more processors are adapted to cause the one or more processors to perform a method comprising:

confirming that the first transaction ending request is allowed to complete; and

responding to each second notification by requesting that the corresponding second server associated with the second notification perform a rollback operation.