System and method for adaptive reliability balancing in distributed programming networks

• US 20030046615A1
• Filed: 12/22/2000
• Published: 03/06/2003
• Est. Priority Date: 12/22/2000
• Status: Abandoned Application

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Stone, Alan
• Application Number:
  US09/741,869
• Publication Number:
  US 20030046615A1
• Time in Patent Office: Days
• US Class Current: 714/47
• CPC Class Codes: G06F 11/008 Reliability or availability analysis
• CPC Class Codes: G06F 2209/508 Monitor
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals
• CPC Class Codes: G06F 9/5083 Techniques for rebalancing the load in a distributed system
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1012 based on compliance of requirements or conditions with available server resources
• CPC Class Codes: H04L 67/1023 based on a hash applied to IP addresses or costs
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer

Abstract

Exemplary embodiments of the invention provide methods and systems for performing reliability balancing, based on past distributed programming network component history, which balances computing resources and their processing components for the purpose of improving the availability and reliability of these resources.

Claims

1. A method for performing reliability balancing in a distributed programming network, the method comprising:

receiving a service request;

identifying at least one object instance associated with the requested service;

querying for data identifying dependencies between the at least one object instance and the requested service;

querying for at least one reliability metric associated with the identified at least one object instance; and

determining which object instance will most reliably fulfill the service request based on that at least one reliability metric.

2. The method of claim 1, wherein determining which object instance will more reliably fulfill the service request is also based on dependencies between the at least one object instance and the requested service.

3. The method of claim 1, wherein determining which object instance will more reliably fulfill the service request is also based on reliability policies of the distributed programming network.

4. The method of claim 1, further comprising matching the service request with at least one object instance based on the determination of which object instance will most reliably fulfill the service request based on the at least one reliability metric.

5. The method of claim 4, wherein matching the service request comprises evaluating at least one reliability metric corresponding to at least one of a history and statistical prediction of future service demand on object instances included in the distributed programming network.

6. A system configured to perform reliability balancing in an operating distributed programming network, the system comprising:

an object resolver configured to identify at least one object instance associated with a requested service from a plurality of object instances coupled together via a control fabric, to query for at least one reliability metric associated with the identified at least one object instance and to make a determination as to which object instance will most reliably fulfill the service request;

a dependency manager coupled to the object resolver, the dependency manager being configured to provide data identifying dependencies between the at least one object instance and the requested service; and

at least one object meter configured to generate the at least one reliability metric regarding at least one object instance.

7. The system of claim 6, wherein the object resolver includes a cost evaluator that has access to reliability policies specific to the distributed programming network.

8. The system of claim 6, wherein the system is configured to retain availability metrics across power and system failures to provide cumulative reliability metrics corresponding to objects and object instances within the distributed programming network.

9. The system of claim 6, wherein the system performs continuous monitoring of the distributed programming network to provide dynamic reliability balancing.

10. The system of claim 6, wherein the system performs matching between service requests and objects to fulfill the service requests by evaluating the availability of at least one object instance to provide the requested service.

11. The system of claim 10, wherein the availability of the object instance is calculated based on a mean time to failure and a mean time to repair.

12. The system of claim 10, wherein the availability of the object instance is calculated as a mean time to failure divided by the sum of the mean time to failure and the mean time to repair.

13. The system of claim 12, wherein the mean time to failure is a time period from an initial instant to a next failure event.

14. The system of claim 13, wherein the mean time to failure is a statistical quantification of system service reliability.

15. The system of claim 12, wherein the mean time to failure is the time to recover from a failure and to restore service accomplishment.

16. The system of claim 15, wherein service accomplishment is achieved when objects working in cooperation to provide the requested service provide the requested service as specified.

17. The system of claim 12, wherein the mean time to repair is a statistical quantification of a service interruption.

18. The system of claim 6, wherein the object resolver evaluates real-time data regarding the operation of at least one object instance or group of object instances.

19. The system of claim 18, wherein the system enables adaptation of service request routing based on changing characteristics of the distributed programming network.

20. The system of claim 19, wherein adaptation is performed in real-time.

21. The system of claim 6, wherein the service request originates from an application or a distributed programming network object that seeks or has requested use one of one or more of the distributed objects.

22. The system of claim 6, wherein service request originates from a client, which generates or is assigned at least one reliability constraint that indicates a level of reliability expected by that client.

23. The system of claim 12, wherein the object resolver is a service that returns reference identification data indicating a particular object and instance of that object that meets the at least one reliability constraint provided by the client.

24. The system of claim 6, wherein the object resolver is a service that returns reference identification data indicating a particular object and instance of that object that meets the at least one reliability constraint provided in the service request.

25. The system of claim 6, wherein the dependency manager is a service that is knowledgeable regarding the topology and dependencies between distributed object instances included in the distributed programming network.

26. The system of claim 6, wherein the object resolver generates a reference to an optimal object instance that meets overall distributed programming network requirements.

27. The system of claim 26, wherein the overall distributed programming network requirements includes at least one reliability policy.

28. The system of claim 6, wherein the data identifying dependencies includes an inventory of what each object or object instance is dependent on.

29. The system of claim 6, wherein the at least one object meter generates at least one reliability metric that is cumulative over time.

30. The system of claim 6, wherein the at least one reliability metric includes or is based on a service sojourn time.

31. The system of claim 6, wherein the at least one reliability metric includes or is based on a service accomplishment time.

32. The system of claim 6, wherein the at least one reliability metric includes or is based on a startup time.

33. A fault tolerance subsystem for improving fault tolerance in a distributed programming network, the fault tolerance subsystem comprising:

a replication manager configured to perform object group management within a distributed programming network including a dependency manager being configured to provide data identifying dependencies between at least one object instance and a requested service;

at least one fault detector configured to receive and respond to queries from the replication manager and monitor a status of objects and object instances within the distributed programming network under the at least one fault detector'"'"'s supervision and configured to generate the at least one reliability metric regarding at least one object instance within the distributed programming network;

a fault notifier coupled to the replication manager and the at least on fault detector and configured to act as a failure notification hub for the at least one fault detector by notifying the replication manager of object or object instance failure following receipt of data indicating detection of such a fault from the at least one fault detector; and

an adaptive placer configured to identify at least one object instance associated with a requested service from a plurality of object instances, to query for at least one reliability metric associated with the identified at least one object instance and to make a determination as to which object instance will most reliably fulfill the service request.

34. The fault tolerance subsystem of claim 33, wherein the object resolver includes a cost evaluator that has access to reliability policies specific to the distributed programming network.

35. The fault tolerance subsystem of claim 33, wherein the service request originates from a client, which generates or is assigned at least one reliability constraint that indicates a level of reliability expected by that client.

36. The fault tolerance subsystem of claim 35, wherein the object resolver is a service that returns reference identification data indicating a particular object and instance of that object that meets the at least one reliability constraint provided by the client.

37. The fault tolerance subsystem of claim 35, wherein the dependency manager is a service that is knowledgeable regarding the topology and dependencies between distributed object instances included in the distributed programming network.