Request queue management

• US 20030126265A1
• Filed: 11/20/2002
• Published: 07/03/2003
• Est. Priority Date: 02/11/2000
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Aziz, Ashar, Patterson, Martin, Gray, Mark, Markson, Thomas
• Granted Patent: US 7,146,233 B2
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: G06F 2209/5021 Priority
• CPC Class Codes: G06F 2209/505 Clust
• CPC Class Codes: G06F 9/45504 Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals

Abstract

Methods and apparatus providing, controlling and managing a dynamically sized, highly scalable and available server farm are disclosed. A Virtual Server Farm (VSF) is created out of a wide scale computing fabric (“Computing Grid”) which is physically constructed once and then logically divided up into VSFs for various organizations on demand. Each organization retains independent administrative control of a VSF. A VSF is dynamically firewalled within the Computing Grid. Allocation and control of the elements in the VSF is performed by a control plane connected to all computing, networking, and storage elements in the computing grid through special control ports. The internal topology of each VSF is under control of the control plane. No physical rewiring is necessary in order to construct VSFs in many different configurations, including single-tier Web server or multi-tier Web-server, application server, database server configurations. Each tier of a multi-tier VSF (e.g., Web server tier, application server tier, database server tier, etc) can be dynamically sized based on the load on the servers in that particular tier. A request queue architecture is also provided for processing work requests that allows selected requests to be blocked until required human intervention is satisfied.

Claims

1. A method for communicating requests for work to be performed between a client and a server, the method comprising the computer-implemented steps of:

receiving from the client a request for work to be performed;

storing the request in a queue;

selecting the request from the queue based upon one or more selection criteria;

if the request includes an attribute that requires human intervention, then not allowing the request to be completely processed until the required human intervention is satisfied; and

once the required human intervention has been satisfied, providing the request to the server.

2. A method as recited in claim 1, where the one or more selection criteria include a priority associated with request.

3. A method as recited in claim 1, where the one or more selection criteria include when the request was received relative to when other requests were received.

4. A method as recited in claim 1, further comprising generating a queue table entry for the request.

5. A method as recited in claim 1, wherein the step of not allowing the request to be completely processed until the required human intervention is satisfied includes not allowing any requests in the queue to be completely processed until the required human intervention is satisfied for the request.

6. A method as recited in claim 1, further comprising:

receiving from the server results of processing the request;

storing the results in the queue; and

providing the results to the client.

7. A method as recited in claim 1, wherein the queue is a persistent queue.

8. A method as recited in claim 1, wherein the request includes an object and a set of one or more methods required to process the object.

9. A computer-readable medium carrying one or more sequences of instructions for communicating requests for work to be performed between a client and a server, the one or more sequences of one or more instructions including instructions which, when executed by one or more processors, cause the one or more processors to perform the steps of:

receiving from the client a request for work to be performed;

storing the request in a queue;

selecting the request from the queue based upon one or more selection criteria;

if the request includes an attribute that requires human intervention, then not allowing the request to be completely processed until the required human intervention is satisfied; and

once the required human intervention has been satisfied, providing the request to the server.

10. A computer-readable medium as recited in claim 9, where the one or more selection criteria include a priority associated with request.

11. A computer-readable medium as recited in claim 9, where the one or more selection criteria include when the request was received relative to when other requests were received.

12. A computer-readable medium as recited in claim 9, further comprising generating a queue table entry for the request.

13. A computer-readable medium as recited in claim 9, wherein the step of not allowing the request to be completely processed until the required human intervention is satisfied includes not allowing any requests in the queue to be completely processed until the required human intervention is satisfied for the request.

14. A computer-readable medium as recited in claim 9, further comprising one or more additional instructions which, when executed by the one or more processors, cause the one or more processors to perform the additional steps of:

receiving from the server results of processing the request;

storing the results in the queue; and

providing the results to the client.

15. A computer-readable medium as recited in claim 9, wherein the queue is a persistent queue.

16. A computer-readable medium as recited in claim 9, wherein the request includes an object and a set of one or more methods required to process the object.

17. A method for processing requests for work to be performed that are stored in a queue, the method comprising the computer implemented steps of:

selecting a request from the queue based upon one or more selection criteria;

if the selected request includes one or more attributes that require human intervention, then not completely processing the selected request until the one or more attributes that require human intervention are satisfied.

18. A method as recited in claim 17, further comprising not completely processing any other requests managed by the queue until the one or more attributes that require human intervention are satisfied.

19. A method as recited in claim 17, wherein the request is selected based upon a set of one or more selection criteria that includes a priority of the request relative to priorities of other requests managed by the queue.

20. A method as recited in claim 17, wherein the request is selected based upon a set of one or more selection criteria that includes when the request was received by the queue relative to when other requests were received by the queue.

21. A method as recited in claim 17, wherein the queue is a persistent queue.

22. A method as recited in claim 17, wherein the request includes an object and a set of one or more methods required to process the object.

23. A computer-readable medium carrying one or more sequences of instructions for processing requests for work to be performed that are stored in a queue, the one or more sequences of one or more instructions including instructions which, when executed by one or more processors, cause the one or more processors to perform the steps of:

selecting a request from the queue based upon one or more selection criteria;

if the selected request includes one or more attributes that require human intervention, then not completely processing the selected request until the one or more attributes that require human intervention are satisfied.

24. A method as recited in claim 23, further comprising not completely processing any other requests managed by the queue until the one or more attributes that require human intervention are satisfied.

25. A method as recited in claim 23, wherein the request is selected based upon a set of one or more selection criteria that includes a priority of the request relative to priorities of other requests managed by the queue.

26. A method as recited in claim 23, wherein the request is selected based upon a set of one or more selection criteria that includes when the request was received by the queue relative to when other requests were received by the queue.

27. A method as recited in claim 23, wherein the queue is a persistent queue.

28. A method as recited in claim 23, wherein the request includes an object and a set of one or more methods required to process the object.

29. A method for communicating requests for work to be performed in a control plane, the method comprising the computer-implemented steps of:

receiving from a master segment manager in the control plane a request for work to be performed;

storing the request in a queue;

selecting the request from the queue based upon one or more selection criteria;

if the request includes an attribute that requires human intervention, then not allowing the request to be completely processed until the required human intervention is satisfied; and

once the required human intervention has been satisfied, providing the request for processing to a slave segment manager in the control plane.

30. A method as recited in claim 29, where the one or more selection criteria include a priority associated with request.

31. A method as recited in claim 29, where the one or more selection criteria include when the request was received relative to when other requests were received.

32. A method as recited in claim 29, further comprising generating a queue table entry for the request.

33. A method as recited in claim 29, wherein the step of not allowing the request to be completely processed until the required human intervention is satisfied includes not allowing any requests in the queue to be completely processed until the required human intervention is satisfied for the request.

34. A method as recited in claim 29, further comprising:

receiving from the slave segment manager results of processing the request;

storing the results in the queue; and

providing the results to the master segment manager.

35. A method as recited in claim 29, wherein the queue is a persistent queue.

36. A method as recited in claim 29, wherein the request includes an object and a set of one or more methods required to process the object.

37. A method as recited in claim 29, wherein the request specifies configuration of a virtual server farm.

38. A computer-readable medium carrying one or more sequences of instructions for communicating requests for work to be performed in a control plane, the one or more sequences of one or more instructions including instructions which, when executed by one or more processors, cause the one or more processors to perform the steps of:

receiving from a master segment manager in the control plane a request for work to be performed;

storing the request in a queue;

selecting the request from the queue based upon one or more selection criteria;

if the request includes an attribute that requires human intervention, then not allowing the request to be completely processed until the required human intervention is satisfied; and

once the required human intervention has been satisfied, providing the request for processing to a slave segment manager in the control plane.

39. A computer-readable medium as recited in claim 38, where the one or more selection criteria include a priority associated with request.

40. A computer-readable medium as recited in claim 38, where the one or more selection criteria include when the request was received relative to when other requests were received.

41. A computer-readable medium as recited in claim 38, further comprising generating a queue table entry for the request.

42. A computer-readable medium as recited in claim 38, wherein the step of not allowing the request to be completely processed until the required human intervention is satisfied includes not allowing any requests in the queue to be completely processed until the required human intervention is satisfied for the request.

43. A computer-readable medium as recited in claim 38, further comprising one or more additional instructions which, when executed by the one or more processors, cause the one or more processors to perform the additional steps of:

receiving from the slave segment manager results of processing the request;

storing the results in the queue; and

providing the results to the master segment manager.

44. A computer-readable medium as recited in claim 38, wherein the queue is a persistent queue.

45. A computer-readable medium as recited in claim 38, wherein the request includes an object and a set of one or more methods required to process the object.

46. A computer-readable medium as recited in claim 38, wherein the request specifies configuration of a virtual server farm.

47. A queue for processing requests for work to be performed, the queue comprising:

a storage medium for storing requests; and

a request processing mechanism communicatively coupled to the storage medium and being configured to;

store requests on the storage medium;

select, based upon one or more selection criteria, a request from the storage medium to be processed;

if the selected request includes one or more attributes that require human intervention, then

determine whether the one or more attributes have been satisfied; and

only provide the request to a recipient if the one or more attributes have been satisfied.

48. A queue as recited in claim 47, wherein the request processing mechanism is further configured to not provide other requests from the storage medium to any recipient if the one or more attributes have not been satisfied.

49. A queue as recited in claim 47, wherein the one or more selection criteria include a priority of the request relative to priorities of other requests managed by the queue.

50. A queue as recited in claim 47, wherein the one or more selection criteria include when the request was received by the queue relative to when other requests were received by the queue.

51. A queue as recited in claim 47, wherein the storage medium is a persistent storage medium.

52. A queue as recited in claim 47, wherein the request includes an object and a set of one or more methods required to process the object.

53. A queue as recited in claim 47, wherein the request processing mechanism is further configured to store results of processing the request on the storage medium.