MANAGING AVAILABILITY OF A COMPONENT HAVING A CLOSED ADDRESS SPACE

• US 20110087919A1
• Filed: 10/13/2009
• Published: 04/14/2011
• Est. Priority Date: 10/13/2009
• Status: Active Grant

• Current Assignee: GlobalFoundries, Inc.
• Original Assignee: International Business Machines Corporation
• Inventors: Shah, Chitrang, Rajagopalan, Sridhar, Raphael, Roger C., Taylor, Paul S., Deshmukh, Harish
• Granted Patent: US 8,082,464 B2
• Time in Patent Office: Days
• US Class Current: 714/4.21
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/3055 Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available error or fault processing without redundancy G06F11/0703; error detection or correction by redundancy in data representation G06F11/08; error detection or correction by redundancy in operation G06F11/14; error detection or correction by redundancy in hardware G06F11/16
• CPC Class Codes: G06F 2209/542 Intercept
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• 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
• CPC Class Codes: H04L 67/59 Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

Systems, methods and articles of manufacture are disclosed for managing availability of a component executing in a distributed system. The component may have an address space closed to the distributed system. In one embodiment, the component may be initiated. A state of the component may be analyzed to determine the availability of the component. The determined availability may be transmitted to the distributed system. The component may also be restarted responsive to a request from the distributed system to restart the component.

Claims

1. A computer-implemented method, comprising:

configuring one or more computer processors to perform an operation for managing availability of a component executing in a distributed system, the component having an address space closed to the distributed system, wherein the operation comprises;

monitoring one or more availability indications of the component within the distributed system;

analyzing the one or more availability indications of the component; and

assigning an availability state to the component within the distributed system based on the of the one or more availability indications of the component.

2. The computer-implemented method of claim 1, wherein the operation further comprises:

initiating execution of the component having the closed address space.

3. The computer-implemented method of claim 1, wherein the operation further comprises:

transmitting the assigned availability state to a second component executing in the distributed system via an availability protocol employed by the distributed system.

4. The computer-implemented method of claim 1, wherein the one or more availability indications of the component are monitored via inter-process communication (IPC) with the component.

5. The computer-implemented method of claim 1, wherein the one or more availability indications of the component are monitored via calling one or more operating system primitives to probe the closed address space of the component.

6. The computer-implemented method of claim 1, wherein the operation further comprises, upon determining that the availability state assigned is a hung state:

killing the component having the closed address space; and

restarting the component having the closed address space.

7. The computer-implemented method of claim 1, wherein the operation further comprises:

receiving a request from a second component executing in the distributed system to restart the component having the closed address space; and

restarting the component having the closed address space.

8. The computer-implemented method of claim 1, wherein the availability state assigned to the component is selected from at least:

(i) a first availability state indicating that the component is healthy;

(ii) a second availability state indicating that the component is hung; and

(iii) a third availability state indicating that the component is dead.

9. A computer-readable storage medium containing a program, which, when executed on a processor, performs an operation for managing availability of a component executing in a distributed system, wherein the operation comprises:

monitoring one or more availability indications of the component within the distributed system, wherein the component has an address space closed to the distributed system;

analyzing the one or more availability indications of the component; and

assigning an availability state to the component within the distributed system based on the of the one or more availability indications of the component.

10. The computer-readable storage medium of claim 9, wherein the operation further comprises:

initiating execution of the component having the closed address space.

11. The computer-readable storage medium of claim 9, wherein the operation further comprises:

transmitting the assigned availability state to a second component executing in the distributed system via an availability protocol employed by the distributed system.

12. The computer-implemented method of claim 9, wherein the one or more availability indications of the component are monitored via inter-process communication (IPC) with the component.

13. The computer-readable storage medium of claim 9, wherein the one or more availability indications of the component are monitored via calling one or more operating system primitives to probe the closed address space of the component.

14. The computer-readable storage medium of claim 9, wherein the operation further comprises, upon determining that the availability state assigned is a hung state:

killing the component having the closed address space; and

restarting the component having the closed address space.

15. The computer-readable storage medium of claim 9, wherein the operation further comprises:

receiving a request from a second component executing in the distributed system to restart the component having the closed address space; and

restarting the component having the closed address space.

16. The computer-readable storage medium of claim 9, wherein the availability state assigned to the component is selected from at least:

(i) a first availability state indicating that the component is healthy;

(ii) a second availability state indicating that the component is hung; and

(iii) a third availability state indicating that the component is dead.

17. A system, comprising:

one or more computer processors; and

a memory containing a program, which when executed by the one or more computer processors is configured to perform an operation for managing availability of a component executing in a distributed system, the component having an address space closed to the distributed system, wherein the operation comprises;

monitoring one or more availability indications of the component within the distributed system;

analyzing the one or more availability indications of the component; and

assigning an availability state to the component within the distributed system based on the of the one or more availability indications of the component.

18. The system of claim 17, wherein the operation further comprises:

initiating execution of the component having the closed address space.

19. The system of claim 17, wherein the operation further comprises:

transmitting the assigned availability state to a second component executing in the distributed system via an availability protocol employed by the distributed system.

20. The system of claim 17, wherein the one or more availability indications of the component are monitored via inter-process communication (IPC) with the component.

21. The system of claim 17, wherein the one or more availability indications of the component are monitored via calling one or more operating system primitives to probe the closed address space of the component.

22. The system of claim 17, wherein the operation further comprises, upon determining that the availability state assigned is a hung state:

killing the component having the closed address space; and

restarting the component having the closed address space.

23. The system of claim 17, wherein the operation further comprises:

receiving a request from a second component executing in the distributed system to restart the component having the closed address space; and

restarting the component having the closed address space.

24. The system of claim 17, wherein the availability state assigned to the component is selected from at least:

(i) a first availability state indicating that the component is healthy;

(ii) a second availability state indicating that the component is hung; and

(iii) a third availability state indicating that the component is dead.