Abstract: A self-healing system configured to automatically restore non-responsive or failed applications to a normal operating state. A self-healing system may restart an application after confirming that the application itself has failed—and not an underlying dependency failure. The self-healing system may also evaluate a server hosting an application reported as being non-responsive to determine whether that server has itself failed. If an application is non-responsive or has failed on an otherwise healthy host, and the dependent service use by the application are available, the self-healing system automatically restores the application to a responsive state. To do so, the self-healing system may generate a run list specifying a sequence of scripts invoked to restore the application to the responsive state.

Abstract: Techniques are disclosed for restoring application services in a computer network. One example method generally includes identifying a set of servers hosting an application and determining a plurality of successive phases for restoring the application. The method further includes identifying a first instance of a first service of the application executing on a first server of the set of servers hosting the application and determining other instances of the first service are unavailable on other servers of the set of servers hosting the application. The method further includes delaying restoration of additional services on the first server until at least a second instance of the first service is available on one or more servers of the set of servers hosting the application other than the first server.

Abstract: A self-healing system configured to automatically restore non-responsive or failed applications to a normal operating state. A self-healing system may restart an application after confirming that the application itself has failed—and not an underlying dependency failure. The self-healing system may also evaluate a server hosting an application reported as being non-responsive to determine whether that server has itself failed. If an application is non-responsive or has failed on an otherwise healthy host, and the dependent service use by the application are available, the self-healing system automatically restores the application to a responsive state. To do so, the self-healing system may generate a run list specifying a sequence of scripts invoked to restore the application to the responsive state.

Abstract: A self-healing system configured to automatically restore non-responsive or failed applications to a normal operating state. A self-healing system may restart an application after confirming that the application itself has failed—and not an underlying dependency failure. The self-healing system may also evaluate a server hosting an application reported as being non-responsive to determine whether that server has itself failed. If an application is non-responsive or has failed on an otherwise healthy host, and the dependent service use by the application are available, the self-healing system automatically restores the application to a responsive state. To do so, the self-healing system may generate a run list specifying a sequence of scripts invoked to restore the application to the responsive state.

Abstract: Techniques are disclosed for restoring application services following a service disruption to a computer network. A faster service restoration (FSR) engine identifies one or more services hosting at least one of the services. The FSR engine identifies dependencies between the service and other application services. The FSR engine generates a run list comprising one or more healing scripts for restoring the services in one or more successive phases. Each successive phase is determined based on the dependencies. Each healing script is associated with one of the services and includes instructions for starting, stopping, and restarting the service. The run list is invoked on each of the servers to restore the application.

Abstract: Techniques are disclosed for restoring application services in a computer network following a service disruption. A faster service restoration (FSR) engine identifies one or more servers hosting a service. The service is associated with dependencies between the service and another one of the services. The FSR engine determines successive phases for restoring the application based on the dependencies. Each phase includes one or more clusters of servers, where each server in the cluster executes an instance one of the services. The FSR engine restores the application by each successive phase. In each phase, the restoration maintains a minimum availability of the instances of the services executed in each cluster.