Configure BESChildProcessKiller Timeout Values
| 0 Votes |
Description
This Task configures the client settings involved with the BESChildProcessKiller task. Two settings are configured -
- BESClient_ChildProcess_Timeout - The current time interval after which stuck BES Child Processes should be terminated
- BESClient_ChildProcess_PreferredTimeout - The normal time interval after which stuck BES Child Processes should be terminated
Keeping both a "current" and "preferred" timeout value on the client allows for a Baseline with known long-running components to set a longer timeout value early in the baseline, execute the long-running tasks, and then revert the client back to a nominal value when the baseline is complete.
Initially, clients should set both values; then, the BESClient_ChildProcess_Timeout value may be manipulated to be longer or shorter than the "preferred" timeout value, then reverted back to the "preferred" timeout value when the off-nominal tasks are completed.
Property Details
| 23047 | |
| Alpha - Code that was just developed | |
| Configure BESChildProcessKiller Timeout Values | |
| BESC | |
| Internal | |
| 12/12/2016 12:00:00 AM | |
| BESChildKiller, Client, Process, Stuck, Client Setting | |
| True | |
| JasonWalker on 12/12/2016 10:30:33 AM | |
| JasonWalker on 12/12/2016 10:30:33 AM | |
| 5115 Views / 14 Downloads | |
* Average over 0 ratings.
** Log In or Register to add your rating.
|
Relevance
Actions
Action 1
// Setup the "current" timeout value for the client
action parameter query "BESClient_ChildProcess_Timeout" with description "Enter a current time interval after which to kill BESClient Child Process (ex %2202:00:00%22 for two hours)" and with default value "02:00:00"
continue if {exists parameter "BESClient_ChildProcess_Timeout" as time interval}
setting "BESClient_ChildProcess_Timeout"="{parameter "BESClient_ChildProcess_Timeout"}" on "{parameter "action issue date" of action}" for client
This action will be considered successful when the applicability relevance evaluates to false.
Action 2
// Setup the "nominal" value for the client
action parameter query "BESClient_ChildProcess_PreferredTimeout" with description "Enter a preferred time interval after which to kill BESClient Child Process (ex %2202:00:00%22 for two hours)" and with default value "02:00:00"
continue if {exists parameter "BESClient_ChildProcess_PreferredTimeout" as time interval}
setting "BESClient_ChildProcess_PreferredTimeout"="{parameter "BESClient_ChildProcess_PreferredTimeout"}" on "{parameter "action issue date" of action}" for client
This action will be considered successful when the applicability relevance evaluates to false.
Action 3
// Revert "current" Timeout to PreferredTimeout value ("normal-up")
if {exists setting "BESClient_ChildProcess_PreferredTimeout" whose (exists value of it as time interval) of client AND not exist setting "BESClient_ChildProcess_Timeout" whose (value of it = value of setting "BESClient_ChildProcess_PreferredTimeout" of client) of client}
setting "BESClient_ChildProcess_Timeout"="{value of setting "BESClient_ChildProcess_PreferredTimeout" of client}" on "{now}" for client
endif
This action will be considered successful when the applicability relevance evaluates to false.
Action 4
// Delete both settings, preventing the Scheduled Task from taking effect
setting delete "BESClient_ChildProcess_Timeout" on "{parameter "action issue date" of action}" for client
setting delete "BESClient_ChildProcess_PreferredTimeout" on "{parameter "action issue date" of action}" for client
This action will be considered successful when the applicability relevance evaluates to false.
Sharing
| Social Media: |
