Dependency management with atomic decay

• US 8,464,270 B2
• Filed: 11/29/2007
• Issued: 06/11/2013
• Est. Priority Date: 11/29/2007
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Little, Mark Cameron
• Primary Examiner(s): Truong, Lechi
• Assistant Examiner(s): Kraft, Shih-Wei
• Application Number:
  US11/998,702
• Publication Number:
  US 20090144305A1
• Time in Patent Office: 2,021 Days
• Field of Search: None
• US Class Current: 718/106
• CPC Class Codes: G06F 16/119 Details of migration of file systems migration mechanisms in storage systems G06F3/0647
• CPC Class Codes: G06F 16/214 Database migration support
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

A dependency is identified between a first component of a distributed computing system and a second component of the distributed computing system if the first component invokes the second component. A dependency map of the distributed computing system that includes the dependency between the first component and the second component is built.

Claims

1. A computer implemented method, comprising:

storing invocation records in a data store by a processor;

determining, by the processor, statistics regarding invocations of a second component of a distributed computing system by a first component of the distributed computing system based on the invocation records;

determining, by the processor, a dependency between the first component and the second component based on the statistics;

determining, by the processor, a dependency rating for the dependency based on the statistics, wherein the dependency rating identifies a degree of dependency between the first component of the distributed computing system and the second component of the distributed computing system;

applying an atomic decay to the dependency rating, wherein the atomic decay reduces a value of the dependency rating over time according to a first atomic decay factor if the dependency includes a first service and according to a second atomic decay factor if the dependency includes a second service;

migrating the first component from a first location to a second different location; and

responsive to determining that the dependency rating for the dependency exceeds a dependency threshold, migrating the second component to the second location.

2. The computer implemented method of claim 1, further comprising:

resetting the dependency rating each time the first component invokes the second component.

3. The method of claim 1, further comprising:

building a dependency map of the distributed computing system that includes the dependency between the first component and the second component, wherein the dependency map includes the dependency rating.

4. The method of claim 1, further comprising:

determining whether the second component has a lower level of redundancy than the first component;

identifying the second component as a potential point of failure if it has a lower level of redundancy than the first component; and

notifying at least one of the first component or an administrator of the first component that the second component is a potential point of failure.

5. The method of claim 1, wherein at least one of the first component or the second component has a unique identification, the method further comprising:

associating at least one of the first component or the second component with the first service or the second service based on the unique identification.

6. A computer readable storage medium including instructions that, when executed by a processor, cause the processor to perform operations comprising:

storing invocation records in a data store by the processor;

determining by the processor, statistics regarding invocations of a second component of a distributed computing system by a first component of the distributed computing system based on the invocation records;

determining, by the processor, a dependency between the first component and the second component based on the statistics;

determining, by the processor, a dependency rating for the dependency based on the statistics, wherein the dependency rating identifies a degree of dependency between the first component of the distributed computing system and the second component of the distributed computing system;

applying an atomic decay to the dependency rating, wherein the atomic decay reduces a value of the dependency rating over time according to a first atomic decay factor if the dependency includes a first service and according to a second atomic decay factor if the dependency includes a second service;

determining that the first component has been migrated or will be migrated from a first location to a second location; and

responsive to determining that the dependency rating for the dependency exceeds a dependency threshold, marking the second component for migration to the second location.

7. The computer readable storage medium of claim 6, the operations further comprising:

migrating the first component from the first location to the second location; and

migrating the second component to the second location.

8. The computer readable storage medium of claim 6, the operations further comprising:

resetting the dependency rating each time the first component invokes the second component.

9. The computer readable storage medium of claim 6, the operations further comprising:

building a dependency map of the distributed computing system that includes the dependency between the first component and the second component.

10. The computer readable storage medium of claim 6, the operations further comprising:

determining whether the second component has a lower level of redundancy than the first component;

identifying the second component as a potential point of failure if it has a lower level of redundancy than the first component; and

notifying at least one of the first component or an administrator of the first component that the second component is a potential point of failure.

11. The computer readable storage medium of claim 6, wherein at least one of the first component or the second component has a unique identification, the operations further comprising:

associating at least one of the first component or the second component with the first service or the second service based on the unique identification.

12. A computer readable storage medium including instructions that, when executed by a processor, cause the processor to perform operations comprising:

storing invocation records in a data store by the processor;

determining, by the processor, a dependency between a first component of a distributed computing system and a second component of the distributed computing system based on invocations of the second component by the first component in the invocation records, wherein the first component has a first unique identification and the second component has a second unique identification;

associating, by the processor, the first component with a first service using the first unique identification and the second component with a second service using the second unique identification;

building, by the processor, a dependency map of the distributed computing system that includes the dependency between the first service and the second service;

applying a dependency rating to the dependency in the dependency map, the dependency rating having an atomic decay with a specified atomic decay factor, wherein the atomic decay reduces a value of the dependency rating over time according to the specified atomic decay factor, and wherein the specified atomic decay factor has a first value if the dependency between the first service and the second service includes a first service type and a second value if the dependency between the first service and the second service includes a second service type;

migrating the first component from a first location to a second location; and

migrating the second component to the second location if the dependency rating has a value that is greater than a dependency threshold.

13. The computer readable storage medium of claim 12, the operations further comprising:

resetting the dependency rating each time the first component invokes the second component.

14. The computer readable storage medium of claim 12, the operations further comprising:

determining whether the second component has a lower level of redundancy than the first component;

identifying the second component as a potential point of failure if it has a lower level of redundancy than the first component; and

notifying at least one of the first component or an administrator of the first component that the second component is a potential point of failure.

15. A computing device comprising:

a memory; and

a processor, coupled to the memory, to;

store invocation records in a data store;

determine statistics regarding invocations of a second component of a distributed computing system by a first component of the distributed computing system based on the invocation records;

determine a dependency between the first component and the second component based on the statistics;

determine a dependency rating for the dependency based on the statistics, wherein the dependency rating identifies a degree of dependency between the first component of the distributed computing system and the second component of the distributed computing system;

apply an atomic decay to the dependency rating, wherein the atomic decay reduces a value of the dependency rating over time according to a first atomic decay factor if the dependency includes a first service and according to a second atomic decay factor if the dependency includes a second service;

migrate the first component from a first location to a second different location; and

migrate the second component to the second location responsive to a determination that the dependency rating for the dependency exceeds a dependency threshold.

16. The computing device of claim 15, wherein the processor is further to:

reset the dependency rating each time the first component invokes the second component.

17. The computing device of claim 15, wherein the processor is further to:

determine whether the second component has a lower level of redundancy than the first component, identify the second component as a potential point of failure if it has a lower level of redundancy than the first component, and notify at least one of the first component or an administrator of the first component that the second component is a potential point of failure.

18. The computing device of claim 15, wherein at least one of the first component or the second component has a unique identification, and wherein the processor is further to:

associate at least one of the first component or the second component with the first service or the second service based on the unique identification.