Fault tolerant rolling software upgrade in a cluster

• US 20060294413A1
• Filed: 06/28/2005
• Published: 12/28/2006
• Est. Priority Date: 06/28/2005
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Filz, Frank S., Jackson, Bruce M., Rao, Sudhir G.
• Application Number:
  US11/168,858
• Publication Number:
  US 20060294413A1
• Time in Patent Office: Days
• US Class Current: 714/4.4
• CPC Class Codes: G06F 11/1433 during software upgrading
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• 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

A method and system are provided for conducting a cluster software version upgrade in a fault tolerant and highly available manner. There are two phases to the upgrade. The first phase is an upgrade of the software binaries of each individual member of the cluster, while remaining cluster members remain online. Completion of the first phase is a pre-requisite to entry into the second phase. Upon completion of the first phase, a coordinated cluster transition is performed during which the cluster coordination component performs any required upgrade to its own protocols and data structures and drives all other software components through the component specific upgrade. After all software components complete their upgrades and any required data conversion, the cluster software upgrade is complete. A shared version control record is provided to manage transition of the cluster members through the cluster software component upgrade.

Claims

1. A method of upgrading software in a cluster, comprising:

reaching software parity for said cluster by individually upgrading software binaries for each member of said cluster to a new software version from a prior version while each cluster member continues to operate at a prior software version; and

coordinating a fault tolerant transition of said cluster to said new software version responsive to reaching software parity while supporting continued access to a clustered application service by application clients during said transition of said cluster to said new software version.

2. The method of claim 1, wherein the step of reaching software parity for said cluster includes each member with said new software version continuing to participate in the cluster under a prior software version until completion of said coordinated transition of all cluster members.

3. The method of claim 1, wherein components of said new software version and said prior software version differ in format.

4. The method of claim 1, wherein the step of coordinating a fault tolerant upgrade of said cluster includes utilizing a cluster leader to drive said upgrade to conclusion, wherein said cluster leader is selected from a group consisting of:

an original cluster leader, and another member of the cluster that has assumed a cluster leader role in event of fault of said original cluster leader.

5. The method of claim 1, wherein the step of coordinating a fault tolerant upgrade of said cluster includes updating a version control record in shared persistent storage.

6. The method of claim 5, further comprising transitioning any node joining said cluster subsequent to a cluster version upgrade through said joining node reading said version control record.

7. A computer system comprising:

a member manager adapted to reach software parity for a cluster through an upgrade of software binaries for each individual member of said cluster to a new software version from a prior version while each cluster member continues to operate at a prior software version; and

a cluster manager adapted to coordinate a fault tolerant transition of said cluster to said new software version, responsive to attainment of software parity by said member manager, and to support continued application service to application clients during said coordinated transition.

8. The system of claim 7, wherein said cluster manager supports continued participation of each cluster member with a new software version in said cluster under a prior software version until completion of execution of said coordinated transition of all cluster members.

9. The system of claim 7, wherein components of said new software version and said prior software version differ in a format.

10. The system of claim 7, wherein a cluster leader drives said upgrade to conclusion and said cluster leader is selected from a group consisting of:

an original cluster leader, and another member of the cluster that has assumed a cluster leader role in event of fault of said original cluster leader.

11. The system of claim 7, wherein said cluster manager updates a version control record in shared persistent storage.

12. The system of claim 11, wherein said cluster manager coordinates transition of any node joining said cluster subsequent to a cluster version upgrade through a read of said version control record by said joining node.

13. An article comprising:

a computer useable medium embodying computer usable program code for upgrading a cluster, said computer program code including;

computer useable program code for reaching software parity for said cluster by individually upgrading software binaries to a new software version from a prior version while each cluster member continues to operate at a prior software version; and

computer useable program code for coordinating a fault tolerant transition of said cluster to said new software version in response to reaching software parity while supporting continued access to a clustered application service by application clients during said transition of said cluster to said new software version.

14. The article of claim 13, wherein said computer useable program code for reaching software parity for said cluster supports continued participation in said cluster of each member with a new software version under said prior software version until completion of said coordinated transition of all cluster members.

15. The article of claim 13, wherein components of said new software version and said prior software version differ in format.

16. The article of claim 13, wherein said computer useable program code for coordinating a fault tolerant transition of said cluster includes utilizing a cluster leader to drive said upgrade to conclusion, wherein said cluster leader is selected from a group consisting of:

an original cluster leader, and another member of the cluster that has assumed a cluster leader role in event of fault of said original cluster leader.

17. The article of claim 13, wherein said computer useable program code for coordinating a fault tolerant transition of said cluster to said new software version includes updating a version control record in shared persistent storage.

18. The article of claim 17, further comprising computer useable program code for transitioning any node joining said cluster subsequent to a cluster version upgrade through said joining node reading said version control record.