Cluster resources

This section describes how to create the cluster resources.

STONITH

The following command creates the STONITH resource. This is to protect your data from being corrupted by rogue nodes or concurrent access in an event of split brain or dual primary situations.

[root@prihana ~]# pcs stonith create <resource-name> fence_aws \
region=<aws-region> \
pcmk_host_map="<primary-hostname>:<primary-instance-id>;<secondary-hostname>:<secondary-instance-id>" \
pcmk_delay_max=45 \
power_timeout=600 pcmk_reboot_timeout=600 \
pcmk_reboot_retries=4 \
op start timeout=600 \
op monitor interval=300 timeout=60       
          

The default pcmk action is reboot. If you want to have the instance remain in a stopped state until it has been investigated and then manually started again, add pcmk_reboot_action=off. Any High Memory (u-*tb1.*) instances or metal instance running on a dedicated host won't support reboot and will require pcmk_reboot_action=off. To do this, update the previously created STONITH resource as:

[root@prihana ~]# pcs stonith create <resource-name> fence_aws \
region=<aws-region> \
pcmk_host_map="<primary-hostname>:<primary-instanceid>;<secondary-hostname>:<secondary-instance-i>" \
pcmk_delay_max=45 pcmk_reboot_action=off \
power_timeout=600 pcmk_reboot_timeout=600 \
pcmk_reboot_retries=4 \
op start timeout=600 \
op monitor interval=300 timeout=60