![]() ![]() # : is the name of the system where group is to be onlined. For executing preonline trigger, VCS invokes following command: hatrigger preonline system service_group whyonlining Īrguments’ details is also available in sample trigger. Preonline trigger in invoked before bringing a service group online. VCS determines if the event is enabled and invokes the hatrigger script, and also passes the name of the event trigger and associated parameters.Į.g. Triggers are executed by hatrigger script located at $VCS_HOME/bin/hatrigger. If you specify an alternate directory, VCS invokes the trigger from that path. You can also relocate this triggers and update TriggerPath accordingly. If a trigger is enabled but the trigger path is "" (default), VCS invokes the trigger from the $VCS_HOME/bin/triggers directory. ![]() Test_sg TriggersEnabled localclus PREONLINE POSTONLINE POSTOFFLINEĮnabling triggers using main.cf Application test_res ( ![]() # hagrp -display test_sg -attribute TriggersEnabled # hagrp -modify test_sg TriggersEnabled PREONLINE POSTONLINE POSTOFFLINE Test_res TriggersEnabled localclus RESFAULT RESNOTOFF RESSTATECHANGE RESADMINWAIT # hares -display test_res -attribute TriggersEnabled As same attribute is used on Resource and Service Group level, steps for enabling/disabling are similar for Resource/Service Group.Įnabling triggers using CLI # hares -modify test_res TriggersEnabled RESFAULT RESNOTOFF RESSTATECHANGE RESADMINWAIT For Service Group level TriggersEnabled attribute, valid values are VIOLATION, NOFAILOVER, PREONLINE, POSTONLINE, POSTOFFLINE, RESFAULT, RESSTATECHANGE, and RESRESTART. For Resource level TriggersEnabled attribute, valid values are RESFAULT, RESNOTOFF, RESSTATECHANGE, RESRESTART, and RESADMINWAIT. This attribute is available on Resource level and Service group level too. You can enable specific triggers on all nodes or only on selected nodes. TriggersEnabled attribute is used to enable/disable by triggers. If you install customized triggers in these directories, you might face issues while upgrading VCS. ![]() It is advised to not put customized trigger scripts in the $VCS_HOME/bin/sample_triggers/VRTSvcs directory or in the $VCS_HOME/bin/internal_triggers directory. TriggersEnabled) that may be required to enable the triggers. For configurable custom triggers, configure other attributes(e.g. To disable non-configurable custom triggers, remove the files associated with the trigger from the $VCS_HOME/bin/triggers directory. To enable non-configurable custom triggers, place the script in $VCS_HOME/bin/triggers directory. Move the modified trigger script to $VCS_HOME/bin/triggers on each node. preonline) while some are non-configurable(e.g. Some custom triggers are configurable(e.g. You may choose to write your own Perl scripts. You can tailor these sample triggers for customized actions according to your requirements. rwxr-r- 1 root root 4037 unable_to_restart_had rwxr-r- 1 root root 2690 unable_to_restart_agent rwxr-r- 1 root root 3324 postonline_rhev # ls -l /opt/VRTSvcs/bin/sample_triggers/VRTSvcs/ With installation, VCS provides a sample Perl script for each event trigger in $VCS_HOME/bin/sample_triggers/VRTSvcs directory. Custom triggers: Custom triggers are configurable at different level. rwxr-x- 1 root root 2349 globalcounter_not_updatedĢ. By default, $VCS_HOME = /opt/VRTSvcs/ # ls -l /opt/VRTSvcs/bin/internal_triggers/ These triggers reside in $VCS_HOME/bin/internal_triggers directory. Internal triggers: Internal triggers are non-configurable and always enabled. Triggers can be broadly categories into 2 categories:ġ. VCS event triggers let you invoke user-defined scripts for specified events in a cluster. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |