Zero downtime mechanism for software upgrade of a distributed computer system

• US 9,229,707 B2
• Filed: 12/18/2008
• Issued: 01/05/2016
• Est. Priority Date: 12/18/2008
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Borissov, Lazar, Brodkorb, Thomas, Driesen, Volker, Georgiev, Anton, Mihalev, Ivan, Mitev, Dencho
• Primary Examiner(s): Vo, Ted T
• Assistant Examiner(s): HUDA, MOHAMMED NURUL
• Application Number:
  US12/337,675
• Publication Number:
  US 20100162226A1
• Time in Patent Office: 2,574 Days
• Field of Search: 717/173, 717/168, 717/170, 717/171.173, 717/175, 717/176
• US Class Current: 1/1
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/656 while running
• CPC Class Codes: G06F 8/658 Incremental updates; Differential updates

Abstract

In a distributed computer system with cluster architecture, a number of service requests are redirected from a first instance of the cluster to a second instance of the cluster for execution. A software patch is applied to one or more software components running on an application server node of the first instance of the cluster. A number of service requests are redirected from the second instance of the cluster to the first instance of the cluster for execution. The software patch is applied on the one or more software components running on an application server node of the second instance of the cluster. A number of new service requests are directed to the upgraded second instance of the cluster for processing.

Claims

1. A computer implemented method for zero downtime software upgrade of a distributed computer system, the method comprising:

receiving a software update for upgrading one or more software components of a plurality of software components running on a plurality of application server nodes of a plurality of instances of a cluster, wherein each instance of the plurality of instances of the cluster runs at least one application server node of the plurality of application server nodes;

redirecting one or more service requests from a first instance of the cluster to a second instance of the cluster for an execution, wherein the one or more service requests are executed by the plurality of software components;

redirecting an execution in progress of a partially executed service request from the first instance of the cluster to the second instance of the cluster, wherein the execution in progress proceeds from a state that is saved on a public store by the first instance of the cluster;

applying the software update to an installation of the one or more software components running on an application server node of the first instance of the cluster, wherein the software update is applied in parallel to the execution of the one or more service requests and with the proceeding execution in progress of the partially executed service request redirected from the first instance to the second instance of the cluster;

redirecting at least one service request from the second instance of the cluster to the upgraded first instance of the cluster for an execution;

redirecting an execution in progress of a partially executed service request from the second instance of the cluster to the upgraded first instance of the cluster, wherein the execution in progress proceeds at the upgraded first instance of the cluster from a state that is saved on the public store by the second instance of the cluster; and

applying the software update to an installation of the one or more software components running on an application server node of the second instance of the cluster, wherein the software update is applied in parallel to the execution of the at least one service request and with the proceeded execution in progress of the partially executed service request redirected from the second instance to the upgraded first instance of the cluster.

2. The method of claim 1, wherein receiving the software update comprises:

in response to receiving the software update, creating a backup copy of the first instance of the cluster comprising the plurality of software components running on the application server node of the first instance of the cluster.

3. The method of claim 1, wherein receiving the software update comprises:

identifying the one or more software components from the plurality of software components running on the plurality of application server nodes of the cluster; and

in response to receiving the software update, ensuring a copy of an original installation of the identified one or more software components, the original installation comprises a current version of the one or more software components.

4. The method of claim 1, wherein redirecting the execution in progress of the partially executed service request from the first instance to the second instance of the cluster comprises:

storing a user session to the public store by a session manager of the first instance of the cluster, the user session keeps a current state of the execution in progress of the partially executed service request redirected from the first instance to the second instance of the cluster;

reading the user session from the public store by a session manager of the second instance of the cluster; and

proceeding with the execution in progress of the partially executed service request redirected from the first instance of the cluster to the second instance of the cluster on the second cluster instance from the current state of the stored user session.

5. The method of claim 1, wherein applying the software update to the installation of the one or more software components running on the application server node of the first instance of the cluster comprises:

applying one or more software upgrades to binary data of the one or more software components, the binary data is stored in the public store; and

synchronizing the installation of the one or more software components running on the application server node of the first instance of the cluster with the upgraded binary data in parallel to the execution of the one or more service requests and with the proceeding execution in progress of the partially executed service request redirected from the first instance to the second instance of the cluster.

6. The method of claim 1, wherein applying the software update to the installation of the one or more software components running on the application server node of the first instance of the cluster comprises:

processing a test service request at the installation of the upgraded one or more software components at the upgraded first instance of the cluster in parallel to the execution of the one or more service requests and with the proceeding execution in progress of the partially executed service request redirected from the first instance to the second instance of the cluster; and

approving the software update or rolling back the software update at the upgraded first instance of the cluster, according to the result of the processing of the test service request.

7. The method of claim 5, wherein applying the software update to the installation of the one or more software components running on the application server node of the second instance of the cluster comprises:

synchronizing the installation of the one or more software components running on the application server node of the second instance of the cluster with the upgraded binary data in parallel to the execution of the at least one service request and with the proceeding execution in progress of the partially executed service request redirected from the second instance to the upgraded first instance.

8. An article of manufacture comprising a non-transitory computer readable storage medium having computer readable instructions stored thereon for execution by a processor to perform a method, the method comprising:

preparing a software patch for upgrading one or more software components of a plurality of software components running on a plurality of application server nodes of a plurality of instances of a cluster, wherein each instance of the plurality of instances of the cluster runs at least one application server node of the plurality of application server nodes;

redirecting one or more service requests from a first instance of the cluster to a second instance of the cluster for an execution, wherein the plurality of service requests are executed by the plurality of software components;

redirecting an execution in progress of a partially executed service request from the first instance of the cluster to the second instance of the cluster, wherein the execution in progress proceeds from a state that is saved on a public store by the first instance of the cluster; and

applying the software patch to an installation of the one or more software components running on an application server node of the first instance of the cluster, wherein the software patch is applied in parallel to the execution of the one or more service requests and with the proceeding execution in progress of the partially executed service request redirected from the first instance to the second instance of the cluster;

redirecting at least one service request from the second instance of the cluster to the upgraded first instance of the cluster for an execution;

redirecting an execution in progress of a partially executed service request from the second instance of the cluster to the upgraded first instance of the cluster, wherein the execution in progress redirected from the second instance to the upgraded first instance of the cluster proceeds at the upgraded first instance of the cluster from a state that is saved on the public store by the second instance of the cluster; and

applying the software patch to the installation of the one or more software components running on an application server node of the second instance of the cluster, wherein the software patch is applied in parallel to the execution of the at least one service request and with the proceeding execution in progress of the partially executed service request redirected from the second instance to the upgraded first instance of the cluster.

9. The article of manufacture of claim 8, wherein redirecting the execution in progress of the partially executed service request from the first instance to the second instance of the cluster comprises:

storing a user session to the public store by a session manager of the first instance of the cluster, the user session keeps a current state of the execution in progress of the partially executed service request redirected from the first instance to the second instance of the cluster;

reading the user session from the public store by a session manager of the second instance of the cluster; and

proceeding with the execution in progress of the partially executed service request redirected from the first instance to the second instance of the cluster on the second cluster instance from the current state of the stored user session.

10. The article of manufacture of claim 8, wherein applying the software patch to the installation of the one or more software components running on the application server node of the first instance of the cluster comprises:

applying one or more software upgrades to binary data of the one or more software components, the binary data is stored in the public store; and

synchronizing the installation of the one or more software components running on the application server node of the first instance of the cluster with the upgraded binary data in parallel to the execution of the one or more service requests and with the proceeding execution in progress of the partially executed service request redirected from the first instance to the second instance of the cluster.

11. The article of manufacture of claim 8, wherein applying the software patch to the installation of the one or more software components running on the application server node of the first instance of the cluster comprises:

routing a test service request from the redirected one or more service requests to the upgraded first instance of the cluster;

processing the test service request at the installation of the upgraded one or more software components at the upgraded first instance of the cluster in parallel to the execution of the one or more service requests and with the proceeding execution in progress of the partially executed service request redirected from the first instance to the second instance of the cluster; and

approving the patch or rolling back the patch, according to the result of the processing of the test service request.

12. A computer system providing zero downtime software upgrade of a distributed computer environment, the system comprising

a memory to store computer executable instructions available at a first instance of a cluster in the distributed computer environment;

and

a processor at the first instance of the cluster coupled to the memory and operable to execute the instructions to;

receive an upgrade for at least one software component of a plurality of software components running on a plurality of server nodes of a plurality of instances of the cluster, wherein each instance of the plurality of instances of the cluster runs at least one application server node of the plurality of application server nodes,

redirect one or more service requests from a first instance of the cluster to a second instance of the cluster for execution, wherein the one or more service requests are executed by the plurality of software components,

redirect an execution in progress of a partially executed service request from the first instance of the cluster to the second instance of the cluster, wherein the execution in progress proceeds from a state that is saved on a public store by the first instance of the cluster,

apply the upgrade to an installation of the at least one software component running on an application server node of the first instance of the cluster, wherein the upgrade is applied in parallel with the execution of the one or more service requests and the proceeded execution in progress of the partially executed service request redirected from the first instance to the second instance of the cluster,

redirect at least one service request from the second instance of the cluster to the upgraded first instance of the cluster for execution,

redirect an execution in progress of a partially executed service request from the second instance of the cluster to the upgraded first instance of the cluster, wherein the execution in progress proceeds at the upgraded first instance of the cluster from a state that is saved on the public store by the second instance of the cluster, and

apply the upgrade to an installation of the at least one software component running on an application server node of the second instance of the cluster, wherein the upgrade is applied in parallel with the execution of the at least one service request and the proceeded execution in progress of the partially executed service request redirected from the second instance to the upgraded first instance of the cluster.

13. The system of claim 12, wherein the memory comprises further instructions executed by the processor to:

in response to receiving the upgrade for the at least one software component of the plurality of software components running at the first instance of the cluster, create a backup copy of the first instance of the cluster comprising the plurality of software components running at the first instance of the cluster.

14. The system of claim 12, wherein the memory comprises further instructions executed by the processor to:

in response to receiving the upgrade for the at least one software component, access an installable current version of the at least one software component.

15. The system of claim 12, wherein applying the upgrade to the at least one software component at the first instance of the cluster comprises:

upgrading binary data of the at least one software component; and

synchronizing the at least one software component running at the first instance of the cluster with the upgraded binary data in parallel with the proceeded execution in progress of the partially executed service request redirected from the first instance to the second instance of the cluster.

16. The system of claim 12, wherein applying the upgrade to the at least one software component at the first instance of the cluster comprises:

processing a test service request at the upgraded at least one software component at the first instance of the cluster in parallel with the proceeded execution in progress of the partially executed service request redirected from the first instance to the second instance of the cluster; and

approving or rolling back the upgrade of the at least one software component at the first instance of the cluster, according to the result of the processing of the test service request.

17. The system of claim 15, wherein applying the upgrade to the at least one software component at the second instance of the cluster comprises:

synchronizing the at least one software component running at the second instance of the cluster with the upgraded binary data in parallel with the proceeded execution in progress of the partially executed service request redirected from the second instance to the upgraded first instance of the cluster.