Active component driven computational server reliability and failure prevention system
An approach for managing and minimized failure of one or more devices in a computerized cluster and/or vehicle infrastructure is disclosed. The proactive approach for mitigating such black swan events as it relate to hardware failures (e.g., servers, network, vehicle systems/architecture, etc.). The approach would proactively inactivate “suspect” components (i.e., components that are completely functional in multiple systems) based on component vintage data from systems where components have failed or malfunctioned. A dedicated service is actively updating suspect components and their respective vintages spread across various systems. Furthermore, the approach backups components using different vintages are effectively utilized to avoid complete system failure.
1 . A computer-implemented method for managing and minimized failure of one or more devices in a computerized cluster, the computer-implemented method comprising:
monitoring a health status of the one or more devices associated with the computerized cluster;
determining whether the one or more devices is malfunctioning;
in responsive to determining that the one or more devices is malfunctioning, determining whether there are backup components of the one or more devices;
in responsive to determining that there are backup components, determining whether the backup components have a different vintage information than the vintage information of the one or more malfunctioning devices;
in responsive to determining that the backup components does not have a different vintage than the one or more malfunctioning devices, activating the backup components; and
in responsive to determining that there are no backup components, managing the one or more malfunctioning devices.
2 . The computer-implemented method of claim 1 , wherein monitoring the health status further comprising:
receiving device data from the one or more devices, wherein device data comprises of connectivity status and operational status; and
updating a device database based on the received data, by changing suspect identifier associated with the one or more devices from a suspect designation to a non-suspect designation and vice versa.
3 . The computer-implemented method of claim 1 , wherein determining whether there are backup components of the one or more devices further comprising:
searching the device database;
identifying whether the backup components resides in the computerized cluster; and
responsive to identifying that the backup components does reside in the computerized cluster, identifying if the backup components are active or inactive based on connectivity.
4 . The computer-implemented method of claim 1 , wherein determining whether the backup components have a different vintage than from the one or more malfunctioning devices further comprising:
retrieving a list from the device database containing the one or more devices; and
comparing the vintage information of the one or more malfunctioning devices against the vintage information of the one or more backup components.
5 . The computer-implemented method of claim 1 further comprising:
in responsive to determining that the backup components is the same vintage as the one or more malfunctioning devices, activating the backup components, wherein the backup components can share the workload.
6 . The computer-implemented method of claim 1 , wherein updating the device database further comprising:
updating the health status in the device database by changing the suspect identifier associated with the one or more devices from a suspect designation to a non-suspect designation and vice versa.
7 . The computer-implemented method of claim 1 further comprising:
selecting the one or more devices with the suspect identifier with the suspect designation for failure analysis and test work based on active component vintage data from a field.
8 . A computer program product for managing and minimized failure of one or more devices in a computerized cluster further comprising:
one or more computer readable storage media having computer-readable program instructions stored on the one or more computer readable storage media, said program instructions executes a computer-implemented method comprising the steps of:
monitoring a health status of the one or more devices associated with the computerized cluster;
determining whether the one or more devices is malfunctioning;
in responsive to determining that the one or more devices is malfunctioning, determining whether there are backup components of the one or more devices;
in responsive to determining that there are backup components, determining whether the backup components have a different vintage information than the vintage information of the one or more malfunctioning devices;
in responsive to determining that the backup components does not have a different vintage than the one or more malfunctioning devices, activating the backup components; and
in responsive to determining that there are no backup components, managing the one or more malfunctioning devices.
9 . The computer program product of claim 8 , wherein monitoring the health status further comprising:
receiving device data from the one or more devices, wherein device data comprises of connectivity status and operational status; and
updating a device database based on the received data, by changing suspect identifier associated with the one or more devices from a suspect designation to a non-suspect designation and vice versa.
10 . The computer program product of claim 8 , wherein determining whether there are backup components of the one or more devices further comprising:
searching the device database;
identifying whether the backup components resides in the computerized cluster; and
responsive to identifying that the backup components does reside in the computerized cluster, identifying if the backup components are active or inactive based on connectivity.
11 . The computer program product of claim 8 , wherein determining whether the backup components have a different vintage than from the one or more malfunctioning devices further comprising:
retrieving a list from the device database containing the one or more devices; and
comparing the vintage information of the one or more malfunctioning devices against the vintage information of the one or more backup components.
12 . The computer program product of claim 8 , further comprising:
in responsive to determining that the backup components is the same vintage as the one or more malfunctioning devices, activating the backup components, wherein the backup components can share the workload.
13 . The computer program product of claim 8 , wherein updating the device database further comprising:
updating the health status in the device database by changing the suspect identifier associated with the one or more devices from a suspect designation to a non-suspect designation and vice versa.
14 . The computer program product of claim 8 , further comprising:
selecting the one or more devices with the suspect identifier with the suspect designation for failure analysis and test work based on active component vintage data from a field.
15 . A computer system for managing and minimized failure of one or more devices in a computerized cluster, the computer system comprising:
one or more computer processors;
one or more computer readable storage media;
one or more computer readable storage media having computer-readable program instructions stored on the one or more computer readable storage media for execution by at least one of the one or more computer processors, said program instructions executes a computer-implemented method comprising the steps of:
monitoring a health status of the one or more devices associated with the computerized cluster;
determining whether the one or more devices is malfunctioning;
in responsive to determining that the one or more devices is malfunctioning, determining whether there are backup components of the one or more devices;
in responsive to determining that there are backup components, determining whether the backup components have a different vintage information than the vintage information of the one or more malfunctioning devices;
in responsive to determining that the backup components does not have a different vintage than the one or more malfunctioning devices, activating the backup components; and
in responsive to determining that there are no backup components, managing the one or more malfunctioning devices.
16 . The computer system of claim 15 , wherein monitoring the health status further comprising:
receiving device data from the one or more devices, wherein device data comprises of connectivity status and operational status; and
updating a device database based on the received data, by changing suspect identifier associated with the one or more devices from a suspect designation to a non-suspect designation and vice versa.
17 . The computer system of claim 15 , wherein determining whether there are backup components of the one or more devices further comprising:
searching the device database;
identifying whether the backup components resides in the computerized cluster; and
responsive to identifying that the backup components does reside in the computerized cluster, identifying if the backup components are active or inactive based on connectivity.
18 . The computer system of claim 15 , wherein determining whether the backup components have a different vintage than from the one or more malfunctioning devices further comprising:
retrieving a list from the device database containing the one or more devices; and
comparing the vintage information of the one or more malfunctioning devices against the vintage information of the one or more backup components.
19 . The computer system of claim 15 , further comprising:
in responsive to determining that the backup components is the same vintage as the one or more malfunctioning devices, activating the backup components, wherein the backup components can share the workload.
20 . The computer system of claim 15 , wherein updating the device database further comprising:
updating the health status in the device database by changing the suspect identifier associated with the one or more devices from a suspect designation to a non-suspect designation and vice versa.