Problem
By default, the VCS_GAB_TIMEOUT is set for 30 seconds (30000 milliseconds).This indicates that if, after 30 seconds GAB has not responded, the High Availability Daemon (HAD) will be restarted. This would occur in environments where the systems are heavily taxed by excessively high CPU and system resource usage. In some instances, it may be necessary to modify the default timeout value to alleviate the issues. Please be advised that while this will eliminate or allow for longer gaps in response time for GAB, it will NOT correct the underlying resource issue on the client's system.
Solution
Example: increase the value from 30 sec to 40 sec.
- Edit the file /opt/VRTSvcs/bin/vcsenv
- Add the following lines to change the gab timeout value to 30000 ms.
VCS_GAB_TIMEOUT=40000; export VCS_GAB_TIMEOUT
------------------------------------------
Note: Cluster needs to be restarted for this change to take effect.
# hastop -all -force
Start VCS on all nodes:
# hastart
You can verify from the engine_A.log the value was changed once you started HAD.
-------------------------------------------
2009/07/15 12:43:19 VCS NOTICE V-16-1-10619 'HAD' starting on: system-02
2009/07/15 12:43:20 VCS INFO V-16-1-10125
GAB timeout set to 40000 ms
-------------------------------------------
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.