System and method for uniquely identifying processes and entities in clusters

• US 8,005,979 B2
• Filed: 10/28/2002
• Issued: 08/23/2011
• Est. Priority Date: 10/28/2002
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Oracle America, Inc. (Oracle Corporation)
• Inventors: Kannan, Mahesh, Dinker, Darpan, Gopinath, Pramod
• Primary Examiner(s): SHAW, PELING ANDY
• Application Number:
  US10/281,543
• Publication Number:
  US 20040098490A1
• Time in Patent Office: 3,221 Days
• Field of Search: 709/238, 709223-226, 709/246, 718/105
• US Class Current: 709/238
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/35 involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function
• CPC Class Codes: H04L 61/50 Address allocation
• CPC Class Codes: H04L 67/01 Protocols

Abstract

Entities within a cluster are uniquely identified with a node ID and an engine ID. The node ID uniquely identifies a node within a cluster of nodes and the engine ID uniquely identifies one of several engines included in the node. Entities may be further identified with a cluster ID, an engine type ID, and/or a virtual server ID. At least some of these IDs may be included in communications received from clients and used to route the communications to the cluster entity identified by the included IDs.

Claims

1. A method, comprising:

receiving a communication from a client;

routing the communication to a node included in a cluster of nodes, wherein the node is identified by a node ID included in the communication; and

routing the communication within the node to an engine of a plurality of engines included in the node, wherein the engine is identified by an engine ID included in the communication;

wherein the node ID uniquely identifies the node among the cluster of nodes and wherein the engine ID uniquely identifies the engine among the plurality of engines included in the node.

2. The method of claim 1, further comprising the engine encoding the node ID and the engine ID in a responsive communication to the client.

3. The method of claim 1, further comprising a router included in the cluster encoding the node ID and the engine ID in the communication in response to said receiving.

4. The method of claim 3, further comprising the router selecting the node ID from a plurality of node IDs dependent on a current load on each of the plurality of nodes identified by a respective one of the plurality of node IDs.

5. The method of claim 3, further comprising the router selecting the node ID from a plurality of node IDs dependent on a physical location of each of the plurality of nodes identified by a respective one of the plurality of node IDs relative to a physical location of the client.

6. The method of claim 3, further comprising the router selecting the node ID from a plurality of node IDs dependent on an engine type ID included in the communication and information identifying one or more engine types included in each of the plurality of nodes identified by a respective one of the plurality of node IDs.

7. The method of claim 6, further comprising the router selecting the engine ID from a plurality of engine IDs dependent on the engine type ID.

8. The method of claim 3, further comprising the router selecting the node ID and the engine ID dependent on a virtual server ID included in the communication and information identifying at least one of a quality of service and a sandbox associated with each engine included in the node.

9. The method of claim 1, wherein the node ID and the engine ID form a hierarchy.

10. The method of claim 1, further comprising routing the communication to the cluster of nodes in response to the communication including an ID uniquely identifying the cluster of nodes among a plurality of clusters.

11. The method of claim 1, further comprising:

receiving a second communication from the client, wherein the second communication includes the node ID and the engine ID;

prior to said receiving the second communication, detecting a failure of the engine identified by the engine ID;

in response to said receiving the second communication, routing the second communication to a second engine identified by a second engine ID dependent on an engine type ID included in the second communication, wherein the engine and the second engine are both an engine type identified by the engine type ID.

12. The method of claim 11, further comprising a node that includes the second engine requesting data from a node including the first engine dependent on the node ID included in the communication.

13. The method of claim 11, further comprising replacing the engine ID in the second communication with the second engine ID.

14. The method of claim 11, wherein said routing the second communication comprises routing the second communication to a second node of the plurality of nodes dependent on the engine type ID included in the second communication, wherein the second node includes the second engine.

15. The method of claim 14, further comprising replacing the node ID in the second communication with a second node ID identifying the second node.

16. The method of claim 11, wherein said routing the second communication to the second engine is further dependent on a virtual server ID included in the second communication.

17. The method of claim 16, wherein the virtual server ID indicates a quality of service to be provided to the client, and wherein the second engine is configured to provide the quality of service.

18. The method of claim 16, wherein the virtual server ID indicates a sandbox associated with the client, and wherein the second engine is configured to operate within the sandbox.

19. The method of claim 1, further comprising:

receiving a second communication from the client, wherein the second communication includes the node ID and the engine ID;

prior to said receiving the second communication, detecting a failure of the node identified by the node ID;

in response to said receiving the second communication, routing the second communication to a second node identified by a second node ID dependent on an engine type ID included in the second communication, wherein the node and the second node include at least one of a type of engine identified by the engine type ID.

20. The method of claim 19, further comprising replacing the node ID in the second communication with the second node ID.

21. The method of claim 19, wherein said routing the second communication to the second node is further dependent on a virtual server ID included in the second communication.

22. The method of claim 19, wherein said routing the second communication to the second node is further dependent on a cluster ID included in the second communication, wherein the cluster ID identifies the cluster that includes the node and the second node.

23. A computing device, comprising:

one or more processors; and

a memory coupled to the one or more processors and configured to store instructions executable by the one or more processors to;

receive a communication that includes a node ID and an engine ID;

route the communication to a node included in a cluster of nodes, wherein the node is uniquely identified among the cluster of nodes by the node ID; and

route the communication within the node to an engine of a plurality of engines included in the node, wherein the engine is uniquely identified among the plurality of engines by an engine ID.

24. The computing device of claim 23, wherein the instructions are further executable to encode the node ID and the engine ID in the communication.

25. The computing device of claim 24, wherein the instructions are further executable to select the node ID from a plurality of node IDs dependent on information identifying a current load on each of the plurality of nodes identified by a respective one of the plurality of node IDs.

26. The computing device of claim 24, wherein the instructions are further executable to select the node ID from a plurality of node IDs dependent on a physical location of each of the plurality of nodes identified by a respective one of the plurality of node IDs relative to a physical location of the client.

27. The computing device of claim 24, wherein the instructions are further executable to select the node ID from a plurality of node IDs dependent on an engine type ID included in the communication and information identifying one or more engine types included in each of the plurality of nodes identified by a respective one of the plurality of node IDs.

28. The computing device of claim 27, wherein the instructions are further executable to select the engine ID from a plurality of engine IDs dependent on the engine type ID.

29. The computing device of claim 24, wherein the instructions are further executable to select the node ID and the engine ID dependent on a virtual server ID included in the communication and information identifying at least one of a quality of service and a sandbox associated with each engine included in the node.

30. The computing device of claim 23, wherein the node ID and the engine ID form a hierarchy.

31. The computing device of claim 23, further comprising a network interface configured to route the communication to the cluster of nodes in response to the communication including an ID uniquely identifying the cluster of nodes among a plurality of clusters.

32. The computing device of claim 23, wherein the instructions are further executable to:

receive a second communication from the client, wherein the second communication includes the node ID and the engine ID;

detect a failure of the engine identified by the engine ID prior to receiving the second communication; and

in response to receiving the second communication and detecting the failure of the engine, route the second communication to a second engine identified by a second engine ID dependent on an engine type ID included in the second communication, wherein the engine and the second engine are both an engine type identified by the engine type ID.

33. The computing device of claim 32, wherein the instructions are further executable to replace the engine ID in the second communication with the second engine ID.

34. The computing device of claim 32, wherein the instructions are further executable to route the second communication by routing the second communication to a second node of the plurality of nodes dependent on the engine type ID included in the second communication, wherein the second node includes the second engine.

35. The computing device of claim 34, wherein the instructions are further executable to replace the node ID in the second communication with a second node ID identifying the second node.

36. The computing device of claim 32, wherein the instructions are further executable to route the second communication to the second engine dependent on a virtual server ID included in the second communication.

37. The computing device of claim 36, wherein the virtual server ID indicates a quality of service to be provided to the client, and wherein the second engine is configured to provide the quality of service.

38. The computing device of claim 36, wherein the virtual server ID indicates a sandbox associated with the client, and wherein the second engine is configured to operate within the sandbox.

39. The computing device of claim 23, wherein the instructions are further executable to:

receive a second communication from the client, wherein the second communication includes the node ID and the engine ID;

detect a failure of the node identified by the node ID prior to receiving the second communication;

in response to receiving the second communication and detecting the failure, route the second communication to a second node identified by a second node ID dependent on an engine type ID included in the second communication, wherein the node and the second node include at least one of a type of engine identified by the engine type ID.

40. The computing device of claim 39, wherein the instructions are further executable to replace the node ID in the second communication with the second node ID.

41. The computing device of claim 39, wherein the instructions are further executable to route the second communication to the second node dependent on a virtual server ID included in the second communication.

42. The computing device of claim 39, wherein the instructions are further executable to route the second communication to the second node dependent on a cluster ID included in the second communication, wherein the cluster ID identifies the cluster that includes the node and the second node.

43. A computer accessible storage medium, comprising instructions computer executable to:

receive a communication that includes a node ID and an engine ID;

route the communication to a node included in a cluster of nodes, wherein the node is uniquely identified among the cluster of nodes by the node ID; and

route the communication within the node to an engine of a plurality of engines included in the node, wherein the engine is uniquely identified among the plurality of engines by an engine ID.

44. The computer accessible storage medium of claim 43, wherein the instructions are further executable to encode the node ID and the engine ID in the communication.

45. The computer accessible storage medium of claim 44, wherein the instructions are further executable to select the node ID from a plurality of node IDs dependent on information identifying a current load on each of the plurality of nodes identified by a respective one of the plurality of node IDs.

46. The computer accessible storage medium of claim 44, wherein the instructions are further executable to select the node ID from a plurality of node IDs dependent on a physical location of each of the plurality of nodes identified by a respective one of the plurality of node IDs relative to a physical location of the client.

47. The computer accessible storage medium of claim 44, wherein the instructions are further executable to select the node ID from a plurality of node IDs dependent on an engine type ID included in the communication and information identifying one or more engine types included in each of the plurality of nodes identified by a respective one of the plurality of node IDs.

48. The computer accessible storage medium of claim 47, wherein the instructions are further executable to select the engine ID from a plurality of engine IDs dependent on the engine type ID.

49. The computer accessible storage medium of claim 44, wherein the instructions are further executable to select the node ID and the engine ID dependent on a virtual server ID included in the communication and information identifying at least one of a quality of service and a sandbox associated with each engine included in the node.

50. The computer accessible storage medium of claim 43, wherein the node ID and the engine ID form a hierarchy.

51. The computer accessible storage medium of claim 43, wherein the instructions are further executable to:

receive a second communication from the client, wherein the second communication includes the node ID and the engine ID;

detect a failure of the engine identified by the engine ID prior to receiving the second communication; and

in response to receiving the second communication and detecting the failure of the engine, route the second communication to a second engine identified by a second engine ID dependent on an engine type ID included in the second communication, wherein the engine and the second engine are both an engine type identified by the engine type ID.

52. The computer accessible storage medium of claim 51, wherein the instructions are further executable to route the second communication by routing the second communication to a second node of the plurality of nodes dependent on the engine type ID included in the second communication, wherein the second node includes the second engine.

53. The computer accessible storage medium of claim 50, wherein the instructions are further executable to route the second communication to the second engine dependent on a virtual server ID included in the second communication.

54. The computer accessible storage medium of claim 53, wherein the virtual server ID indicates a quality of service to be provided to the client, and wherein the second engine is configured to provide the quality of service.

55. The computer accessible storage medium of claim 53, wherein the virtual server ID indicates a sandbox associated with the client, and wherein the second engine is configured to operate within the sandbox.

56. The computer accessible storage medium of claim 43, wherein the instructions are further executable to:

receive a second communication from the client, wherein the second communication includes the node ID and the engine ID;

detect a failure of the node identified by the node ID prior to receiving the second communication;

in response to receiving the second communication and detecting the failure, route the second communication to a second node identified by a second node ID dependent on an engine type ID included in the second communication, wherein the node and the second node include at least one of a type of engine identified by the engine type ID.

57. The computer accessible storage medium of claim 56, wherein the instructions are further executable to replace the node ID in the second communication with the second node ID.

58. The computer accessible storage medium of claim 56, wherein the instructions are further executable to route the second communication to the second node dependent on a virtual server ID included in the second communication.

59. The computer accessible storage medium of claim 56, wherein the instructions are further executable to route the second communication to the second node dependent on a cluster ID included in the second communication, wherein the cluster ID identifies the cluster that includes the node and the second node.

60. A system, comprising:

means for routing a communication received from a client to a node of a plurality of nodes included in a cluster dependent on a node ID included in the communication, wherein the node ID uniquely identifies the node among the plurality of nodes; and

means for routing the communication within the node to an engine of a plurality of engines included in the node dependent on an engine ID included in the communication, wherein the engine ID uniquely identifies the engine among the plurality of engines included in the node.