Method and system for managing high-availability-aware components in a networked computer system

• US 7,143,167 B2
• Filed: 05/02/2001
• Issued: 11/28/2006
• Est. Priority Date: 05/02/2000
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Shokri, Eltefaat H., Herrmann, Frederic, Kampe, Mark A., Nguyen, Gia-Khanh
• Primary Examiner(s): Etienne, Ario
• Assistant Examiner(s): EL CHANTI, HUSSEIN A
• Application Number:
  US09/846,380
• Publication Number:
  US 20010054095A1
• Time in Patent Office: 2,036 Days
• Field of Search: 709/201, 709208-209, 709/211, 709220-224, 709217-219, 709223-226
• US Class Current: 709/226
• CPC Class Codes: G06F 11/202 where processing functionality is redundant redundant communication control functionality G06F11/2005, redundant storage control functionality G06F11/2089
• CPC Class Codes: G06F 11/2025 using centralised failover control functionality
• CPC Class Codes: G06F 11/2051 in regular structures

Abstract

The present invention describes a method and system for managing high-availability-aware components in a networked computer system. In particular, the method includes registering components and dynamically allocating roles and assignments to one or more of the registered components to achieve a desired level of redundancy based on component type information. The method may include an additional step of performing administrative actions on the registered components in response to a request from an external management agent in order to increase the availability of services provided by the high-availability-aware components. Further, the method may additionally include responding to an error by changing roles and assignments of one or more of the registered components, providing information to registered components so that related components may communicate to achieve a desired redundancy level, and/or maintaining additional information relevant to managing high-availability-aware components. Such additional information may include information regarding software release domains, component relationships, and/or protection groups.

Claims

1. A method of allocating an assignment to a plurality of high-availability-aware applications in a networked computer system, the method comprising;

registering the plurality of high-availability-aware applications through an application programming interface;

allocating roles to registered applications of the plurality of high-availability-aware applications by invoking a callback interface of the registered applications;

maintaining application relationship information;

selecting a first application from the registered applications based on application type information and the application relationship information;

allocating the assignment to the first application by invoking a callback interface of the first application;

changing a role of the first application to primary by invoking a callback interface of the first application;

determining a redundancy level based on the application type information;

selecting a predetermined number of secondary applications from the registered applications based on application type information of the secondary applications and the application relationship information, wherein the predetermined number is based on the determined redundancy level;

changing roles of the predetermined number of secondary applications to secondary by invoking a callback interface of the secondary applications; and

notifying the first application, by invoking a callback interface of the first application, about the predetermined number of secondary applications and the predetermined number of secondary applications, by invoking a callback interface of the secondary applications, about the first application.

2. The method of claim 1, further comprising:

detecting an error affecting the first application;

selecting a new primary application from the predetermined number of secondary applications using the application relationship information; and

changing a role of the new primary application to primary by invoking a callback interface of the new primary application.

3. The method of claim 2, further comprising:

instructing the first application to communicate information to the new primary application by invoking a callback interface of the first application.

4. The method of claim 1, further comprising:

maintaining software release domain information, wherein the software release domain information is included in the notifying step.

5. The method of claim 1, further comprising:

performing administrating actions on the registered applications in response to a request from an external management agent.

6. A computer program product stored on a tangible computer readable medium for allocating an assignment in a networked computer system, the computer program product comprising

computer readable program code configured to provide an application programming interface to register a plurality of high-availability-aware applications components;

computer readable program code configured to allocate roles to registered applications components of the plurality of high-availability-aware applications by invoking a callback interface of the registered applications;

computer readable program code configured to allocate the assignment to a first application selected from the registered applications based on application type information of the first application by invoking a callback interface of the first application;

computer readable program code configured to change a role of the first application to primary by invoking a callback interface of the first application;

computer readable program code configured to determine a redundancy level based on the application type information;

computer readable program code configured to allocate the assignment to a predetermined number of secondary applications selected from the registered applications based on application type information of the secondary components, wherein the predetermined number is based on the redundancy level by invoking a callback interface of the secondary applications;

computer readable program code configured to change roles of the predetermined number of secondary applications to secondary by invoking a callback interface of the second applications;

computer readable program code configured to notify the first application by invoking a callback interface of the first application about the predetermined number of secondary applications and the predetermined number of secondary applications about the first application by invoking a callback interface of the secondary applications; and

a computer readable medium having the computer readable program codes embodied therein.

7. The computer program product of claim 6, further comprising:

computer readable program code configured to detect an error affecting the first application;

computer readable program code configured to select a new primary application from the predetermined number of secondary applications; and

computer readable program code configured to change a role of the new primary application to primary by invoking a callback interface of the new primary application.

8. A system for allocating an assignment in a networked computer system, the system comprising:

means for registering a plurality of high-availability-aware applications through an application programming interface;

means for allocating roles to registered applications of the plurality of high-availability-aware applications by invoking a callback interface of the registered applications;

means for allocating the assignment to a first application selected from the registered applications based on application type information of the first application by invoking a callback interface of the first application;

means for changing a role of the first application to primary by invoking a callback interface of the first application;

means for determining a redundancy level based on the application type information;

means for allocating the assignment to a predetermined number of secondary applications selected from the registered applications based on application type information of the secondary applications, wherein the predetermined number is based on the redundancy level by invoking a callback interface of the secondary applications;

means for changing roles of the predetermined number of secondary applications to secondary by invoking a callback interface of the secondary applications; and

means for notifying the first application about the predetermined number of secondary applications by invoking a callback interface of the first application and the predetermined number of secondary applications components about the first application by invoking a callback interface of the secondary applications.

9. A mechanism configured to manage a plurality of high-availability-aware applications in a networked computer system, the mechanism comprising:

a mechanism configured to register through an application programming interface the plurality of high-availability-aware applications to be managed; and

a mechanism configured to dynamically allocate roles and assignments to registered applications of the plurality of high-availability-aware applications to achieve a desired redundancy level based on application type information by invoking a callback interface of the registered applications.

10. The mechanism of claim 9, further comprising:

a mechanism configured to respond to an error by changing roles and assignments of the registered applications by invoking a callback interface of the registered applications.

11. The mechanism of claim 9, further comprising:

a mechanism configured to provide information to the registered applications so that related applications among the registered applications may communicate to achieve the desired redundancy level.

12. The mechanism of claim 9, further comprising:

a mechanism configured to perform administrative actions on the registered applications in response to a request from an external management agent.

13. The mechanism of claim 9, further comprising:

a mechanism configured to maintain additional information relevant to managing the registered applications.

14. The mechanism of claim 13, wherein the additional information includes information regarding software release domains, application relationships, and protection groups.