Orchestration of software applications upgrade using automatic hang detection

Patent metadata

Field	Value
Publication number	US-2016124741-A1
Application number	US-201514925354-A
Country	US
Kind code	A1
Filing date	Oct 28, 2015
Priority date	Oct 29, 2014
Publication date	May 5, 2016
Grant date	—

Abstract

In an upgrade infrastructure performing an overall upgrade operation comprising multiple upgrade processes being executed, possibly concurrently, on multiple hosts for upgrading one or more software applications hosted by hosts, automated hang detection mechanisms are disclosed for quickly, efficiently, and automatically detecting when one or more of the upgrade process are in a hang state. Different hang detection techniques are described including a metadata-driven hang detection mechanism and a code-driven hang detection mechanism.

First claim

What is claimed is:

1 . A method comprising:
monitoring execution of a first upgrade process on a first host machine, the first upgrade process upgrading a first software application on the first host machine; accessing, by a computing system, runtime execution timing data for the first upgrade process, the runtime execution timing data captured for the first upgrade process during the monitoring of the execution of the first upgrade process; comparing, by the computing system, the runtime execution timing data associated with the first upgrade process to a first reference timing data specified for the first upgrade process for the first host machine, wherein the first reference timing data is different from a second reference timing data specified for the first upgrade process for a second host machine different from the first host machine; determining, by the computing system, based upon the comparing, that the first upgrade process executing on the first host machine is to be indicated as being in a hang state; and generating, by the computing system, a hang alert message indicating the first upgrade process executing on the first host machine is in the hang state.

2 . The method of claim 1 , wherein accessing the runtime execution timing data includes:
receiving the runtime execution timing data from the first upgrade process; or retrieving the runtime execution timing data from the first upgrade process; or retrieving the runtime execution timing data from a storage, wherein the first upgrade process writes the runtime execution timing data to the storage.

3 . The method of claim 1 , wherein:
the first reference timing data includes a first reference execution time for the first upgrade process; determining that the first upgrade process is to be indicated as being in the hang state comprises:
determining, based upon the runtime execution timing data, a current execution time indicative of a time that the first upgrade process is executing on the first host machine; and
determining that the current time has exceeded the first reference execution time.

4 . The method of claim 1 , wherein:
the first reference timing data includes a first reference execution time and a first latency tolerance time associated with the first upgrade process; determining that the first upgrade process is to be indicated as being in the hang state comprises:
determining, based upon the runtime execution timing data, a current execution time indicative of a time that the first upgrade process is executing on the first host machine; and
determining that the current time has exceeded the first reference execution time plus the first latency tolerance time.

5 . The method of claim 1 , wherein the first reference timing data includes a first reference execution time of the first upgrade process, the method further comprising:
determining a latency tolerance time for the first upgrade process based on the runtime execution timing data associated with the first upgrade process, wherein the latency tolerance time is a buffer provided on top of the first reference execution time; and generating the hang alert message upon determining that the first upgrade process continues execution after a total of the first reference execution time and the first latency tolerance time has passed.

6 . The method of claim 1 , further comprising:
monitoring execution of a second upgrade process on the first host machine, the second upgrade process upgrading a second software application on the first host machine; accessing, by a computing system, runtime execution timing data for the second upgrade process, the runtime execution timing data captured for the second upgrade process during the monitoring of the execution of the first upgrade process; comparing, by the computing system, the runtime execution timing data associated with the second upgrade process to a first reference timing data specified for the second upgrade process for the first host machine, wherein the first reference timing data is different from a second reference timing data specified for the second upgrade process for the second host machine; determining, by the computing system, based upon the comparing, that the second upgrade process executing on the first host machine is to be indicated as being in a hang state; and generating, by the computing system, a hang alert message indicating the second upgrade process executing on the first host machine is in the hang state.

7 . The method of claim 1 , wherein the first reference timing data includes a time length or a time of completion for execution of the first upgrade process on the first host machine.

8 . The method of claim 1 , wherein the first reference timing data is pre-determined prior to the execution of the first upgrade process on the first host machine or the first reference timing data is determined during execution of the first upgrade process on the first host machine.

9 . A non-transitory computer-readable storage memory storing a plurality of instructions executable by one or more processors, the plurality of instructions comprising:
instructions that cause at least one processor from the one or more processors to monitor execution of a first upgrade process on a first host machine, the first upgrade process upgrading a first software application on the first host machine; instructions that cause at least one processor from the one or more processors to access runtime execution timing data for the first upgrade process, the runtime execution timing data captured for the first upgrade process during the monitoring of the execution of the first upgrade process; instructions that cause at least one processor from the one or more processors to compare the runtime execution timing data associated with the first upgrade process to a first reference timing data specified for the first upgrade process for the first host machine, wherein the first reference timing data is different from a second reference timing data specified for the first upgrade process for a second host machine different from the first host machine; instructions that cause at least one processor from the one or more processors to determine, based upon the comparing, that the first upgrade process executing on the first host machine is to be indicated as being in a hang state; and instructions that cause at least one processor from the one or more processors to generate a hang alert message indicating the first upgrade process executing on the first host machine is in the hang state.

10 . The non-transitory computer-readable storage memory of claim 9 , wherein the instructions that cause at least one processor from the one or more processors to access runtime execution timing data associated with the first upgrade process based on monitoring further comprise:
instructions that cause at least one processor from the one or more processors to receive the runtime execution timing data from the first upgrade process; or instructions that cause at least one processor from the one or more processors to retrieve the runtime execution timing data from the first upgrade process; or instructions that cause at least one processor from the one or more processors to retrieve the runtime execution timing data from a storage, wherein the first upgrade process writes the runtime execution timing data to the storage.

11 . The non-transitory computer-readable storage memory of claim 9 , wherein:
the first reference timing data includes a first reference execution time for the first upgrade process; instructions that cause at least one processor from the one or more processors to determine that the f

Assignees

• Oracle Int Corp

Inventors

• Hu Fang
• Vong Chi Kin
• Thiagarajan Bhuvaneswari
• Richardson Tim
• Lu Jinghuan Jay

Classifications

• H04L67/34

  involving the movement of software or configuration parameters  (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title

• G06F8/65 Primary

  Updates (security arrangements therefor G06F21/57) · CPC title