InfoScale™ 9.0 Cluster Server Agent Developer's Guide - AIX, Linux, Solaris, Windows
- Introduction
- Agent entry point overview
- About agent entry points
- Agent entry points described
- About the action entry point
- About the info entry point
- Considerations for using C++ or script entry points
- About the agent information file
- About the ArgList and ArgListValues attributes
- Creating entry points in C++
- About creating entry points in C++
- Syntax for C++ entry points
- Agent framework primitives
- Agent Framework primitives for container support
- Creating entry points in scripts
- About creating entry points in scripts
- Syntax for script entry points
- Agent framework primitives
- VCSAG_GET_ATTR_VALUE
- Agent Framework primitives with container support
- Example script entry points
- Logging agent messages
- Building a custom agent
- Building a script based IMF-aware custom agent
- Creating XML file required for AMF plugins to do resource registration for online and offline state monitoring
- Testing agents
- Static type attributes
- About static attributes
- Static type attribute definitions
- AdvDbg
- ArgList
- State transition diagram
- Internationalized messages
- Troubleshooting VCS resource's unexpected behavior using First Failure Data Capture (FFDC)
- Appendix A. Using pre-5.0 VCS agents
ActionTimeout
After the hares -action command has instructed the agent to perform a specified action, the agent waits for the number of seconds as specified in the ActionTimeout attribute (scalar-integer) to let the action entry point finish and after the time limit has been reached the agent terminates the running action entry as it might hung at any point. The value of ActionTimeout may be set for individual resources, if overridden.
The default is 30 seconds. The value of the ActionTimeout attribute is internally capped at MonitorInterval / 2.
If the ActionTimeout attribute is set to a value greater than MonitorInterval/2, then MonitorInterval/2 is used instead of ActionTimeout. If ActionTimeout value is less than MonitorInterval/2, then the ActionTimeout value is honored.
Note:
You can extend this value by using the VCSAgSetResEPTimeout (for C/C++ entry point) /VCSAG_SET_RES_EP_TIMEOUT (for script entry point). Use this API cautiously as setting a value higher than MonitorInterval / 2 might result in delay of next periodic monitor which is used to check the state of the resource.
See VCSAgSetResEPTimeout.