Method and system for determining favorability of upgrade window

A non-transitory computer readable medium comprising computer readable program code, which when executed by a computer processor enables the computer processor to perform a method for managing updates of a data manager, the method comprising:

• identifying, by a distributed control manager of the data manager, a service update event, wherein the data manager comprises services;
• in response to identifying the service update event:
• identifying a service sub-tree based on a service call graph;
• generating an update sequence for the service sub-tree using the service call graph;
• predicting an update window for the service sub-tree based on a risk profile for a service specified in the service sub-tree;
• selecting a first service of the service sub-tree based on the update sequence, wherein the first service comprises a first standby service instance and a first active service instance;
• generating a backup of a first portion of a services shared data volume repository associated with the first service;
• applying a first portion of an update to the first standby service instance to obtain a first updated active service instance;
• making a first determination that a first performance and reliability check associated with the first updated active service instance is below a threshold;
• and
• in response to the first determination:
• applying the first portion of the update to a second standby service instance, wherein the second standby service instance comprises the first active service instance.

A system for managing updates of a data manager, the system comprising:

• the data manager comprising services;
• a distributed control manager of the data manager, comprising a processor and memory, configured to:
• identify a service update event, wherein the data manager comprises services;
• in response to identifying the service update event:
• identifying a service sub-tree based on a service call graph;
• generating an update sequence for the service sub-tree using the service call graph;
• predicting an update window for the service sub-tree based on a risk profile for a service specified in the service sub-tree;
• selecting a first service of the service sub-tree based on the update sequence, wherein the first service comprises a first standby service instance and a first active service instance;
• generating a backup of a first portion of a services shared data volume repository associated with the first service;
• applying a first portion of an update to the first standby service instance to obtain a first updated active service instance;
• making a first determination that a first performance and reliability check associated with the first updated active service instance is below a threshold;
• and
• in response to the first determination:
• applying the first portion of the update to a second standby service instance, wherein the second standby service instance comprises the first active service instance.