Dynamically Adjusting Operating Level of Server Processing Responsive to Detection of Failure at a Server

• US 20070233865A1
• Filed: 03/30/2006
• Published: 10/04/2007
• Est. Priority Date: 03/30/2006
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Trisko, Kenneth, Garbow, Zachary, McDaniel, Clayton, Hamlin, Robert
• Application Number:
  US11/278,019
• Publication Number:
  US 20070233865A1
• Time in Patent Office: Days
• US Class Current: 709/226
• CPC Class Codes: G06F 11/0796 Safety measures, i.e. ensuring safe condition in the event of error, e.g. for controlling element
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

A facility is provided for dynamically adjusting operating level of server processing within a computing environment including one or more servers processing multiple types of server tasks. The facility includes, responsive to detection of a failure at a server of the environment, determining a situational severity threshold for continued computing environment task processing, and automatically comparing the threshold against priority metrics for the multiple types of server tasks processed within the environment. Server processing of one or more types of server tasks having a priority metric below the situational severity threshold is then automatically blocked. The facility can also include dynamically adjusting of at least one priority metric associated with at least one type of server task to reflect a cause of the failure of the server, wherein the dynamically adjusting occurs prior to the automatic comparing of the situational severity threshold against the priority metrics.

Claims

1. A method of dynamically adjusting operating level of server processing within a computing environment, the computing environment including one or more servers processing multiple types of server tasks, the method comprising:

responsive to detecting failure at a server of the computing environment, determining a situational severity threshold for continued computing environment task processing;

comparing the situational severity threshold with priority metrics for the multiple types of server tasks processed by the computing environment; and

blocking server processing of one or more types of server tasks having a priority metric below the situational severity threshold.

2. The method of claim 1, further comprising dynamically adjusting at least one priority metric associated with at least one type of server task of the multiple types of server tasks to reflect a cause of the failure of the server, the dynamically adjusting occurring prior to the comparing and the blocking.

3. The method of claim 1, wherein the dynamically adjusting comprises automatically updating the at least one priority metric of at least one type of server task of the multiple types of server tasks in a task priority list to reflect a cause of the failure at the server, the task priority list comprising a defined priority metric for each type of server task of the multiple types of server tasks processed by the computing environment.

4. The method of claim 3, wherein the automatically updating comprises automatically reducing the priority metric of the at least one type of server task to inhibit processing thereof responsive to the comparing of the situational severity threshold with the priority metrics and the blocking server processing of the one or more types of server tasks.

5. The method of claim 4, wherein the automatically reducing of the priority metric of the at least one type of server task comprises reducing the priority metric by an amount proportional to a determined confidence level of an identification of a cause of the failure at the server being execution of the at least one type of server task.

6. The method of claim 3, wherein the priority metric of each type of task is derived, in part, from a number of resources required by the type of task, and a historic risk level of the type of task, derived from how often the type of task has caused server failure in the past, and wherein the method further comprises predefining a priority metric for each type of server task in the task priority list, the automatically updating comprising automatically reducing at least one predefined priority metric of the at least one type of server task to reflect the cause of the failure at the server.

7. The method of claim 1, wherein the computing environment comprises a server in a standalone computing environment, and the detected failure is at the server, and wherein the blocking comprises continuing task processing by the server in a restricted task processing mode wherein only critical task processing of the computing environment above the situational severity threshold is maintained.

8. The method of claim 1, wherein the computing environment comprises a cluster of servers comprising at least the server having the detected failure and a backup server thereto, and wherein the method further comprises transitioning server processing of tasks to the backup server responsive to detection of the failure, and wherein the blocking comprises blocking task processing at the backup server having a priority metric below the situational severity threshold, thereby ensuring critical task processing at the backup server.

9. The method of claim 1, wherein the blocking further comprises determining whether the failing server is part of a cluster, and if so, shutting down a backup server'"'"'s processing of tasks with priority metrics below the situational severity threshold, otherwise, notifying the server having the failure to block processing of tasks with priority metrics below the situational severity threshold, and continuing restricted task processing at the server having the failure.

10. The method of claim 1, wherein determining the situational severity threshold comprises rating the server failure in comparison with importance of maintaining server processing, and wherein the rating comprises calculating the situational severity threshold employing a plurality of administrator-weighted factors, the administrator-weighted factors including at least some of:

time of day, predefined server service level commitments, status of the failing server, and number of current users of the one or more servers of the computing environment.

11. A system of adjusting operating level of server processing within a computing environment, the computing environment including one or more servers processing multiple types of server tasks, the system comprising:

means for determining a situational severity threshold for continued computing environment task processing by the one or more servers responsive to detecting failure at a server of the computing environment;

means for comparing the situational severity threshold with priority metrics, each priority metric being associated with a different type of server task of the multiple types of server tasks processed by the computing environment; and

means for blocking processing of one or more types of server tasks having a priority metric below the situational severity threshold.

12. The system of claim 11, further comprising means for dynamically adjusting at least one priority metric associated with at least one type of server task of the multiple types of server tasks to reflect a cause of the failure of the server, the dynamically adjusting occurring prior to the comparing and the blocking.

13. The system of claim 12, wherein the means for dynamically adjusting comprises means for automatically reducing the priority metric of the at least one type of server task to inhibit processing thereof responsive to the comparing of the situational severity threshold with the priority metrics and the blocking server processing of the one or more types of server tasks.

14. The system of claim 13, wherein the means for automatically reducing of the priority metric of the at least one type of server task comprises means for reducing the priority metric by an amount proportional to a determined confidence level of an identification of a cause of the failure at the server being execution of the at least one type of server task.

15. The system of claim 14, wherein the priority metric of each type of task is derived, in part, from a number of resources required by the type of task, and a historic risk level of the type of task, derived from how often the type of task has caused server failure in the past, and wherein the system further comprises means for predefining a priority metric for each type of server task in the task priority list, the means for automatically updating comprising means for automatically reducing at least one predefined priority metric of the at least one type of server task to reflect the cause of the failure at the server.

16. The system of claim 11, wherein the means for blocking further comprises means for determining whether the failing server is part of a cluster, and if so, for shutting down a backup server'"'"'s processing of tasks with priority metrics below the situational severity threshold, otherwise, for notifying the server having the failure to block processing of tasks with priority metrics below the situational severity threshold, and for continuing restricted task processing at the server having the failure.

17. The system of claim 11, wherein the means for determining the situational severity threshold comprises means for rating the server failure in comparison with importance of maintaining server processing, and wherein the means for rating comprises means for calculating the situational severity threshold employing a plurality of administrator-weighted factors, the administrator-weighted factors including at least some of:

time of day, predefined server service level commitments, status of the failing server, and number of current users of the one or more servers of the computing environment.

18. At least one program storage device readable by a computer, tangibly embodying at least one program of instructions executable by the computer to perform a method of adjusting operating level of server processing within a computing environment, the computing environment including one or more servers processing multiple types of server tasks, the method comprising:

responsive to detecting failure at a server of the computing environment, determining a situational severity threshold for continued computing environment task processing;

comparing the situational severity threshold with priority metrics for the multiple types of server tasks processed by the computing environment; and

blocking server processing of one or more types of server tasks having a priority metric below the situational severity threshold.

19. The at least one program storage device of claim 18, further comprising dynamically adjusting at least one priority metric associated with at least one type of server task of the multiple types of server tasks to reflect a cause of the failure of the server, the dynamically adjusting occurring prior to the comparing and the blocking.

20. The at least one program storage device of claim 19, wherein the dynamically adjusting of the at least one priority metric associated with the at least one type of server task comprises automatically reducing the priority metric by an amount proportional to a determined confidence level of an identification of a cause of the failure at the server being execution of the at least one type of server task.

21. The at least one program storage device of claim 20, wherein the priority metric of each type of task is derived, in part, from a number of resources required by the type of task, and a historic risk level of the type of task, derived from how often the type of task has caused server failure in the past, and wherein the method further comprises predefining a priority metric for each type of server task in the task priority list, the automatically reducing comprising automatically reducing at least one predefined priority metric of the at least one type of server task to reflect the cause of the failure at the server.

22. The at least one program storage device of claim 18, wherein the blocking further comprises determining whether the failing server is part of a cluster, and if so, shutting down a backup server'"'"'s processing of tasks with priority metrics below the situational severity threshold, otherwise, notifying the server having the failure to block processing of tasks with priority metrics below the situational severity threshold, and continuing restricted task processing at the server having the failure.

23. The at least one program storage device of claim 18, wherein determining the situational severity threshold comprises rating the server failure in comparison with importance of maintaining server processing, and wherein the rating comprises calculating the situational severity threshold employing a plurality of administrator-weighted factors, the administrator-weighted factors including at least some of:

time of day, predefined server service level commitments, status of the failing server, and number of current users of the one or more servers of the computing environment.