Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
2.5. Testing the Resource Configuration
In the cluster status display shown in Section 2.4, “Creating the Resources and Resource Groups with the pcs Command”, all of the resources are running on node
z1.example.com. You can test whether the resource group fails over to node z2.example.com by using the following procedure to put the first node in standby mode, after which the node will no longer be able to host resources.
- The following command puts node
z1.example.cominstandbymode.root@z1 ~]# pcs node standby z1.example.com
root@z1 ~]# pcs node standby z1.example.comCopy to Clipboard Copied! Toggle word wrap Toggle overflow - After putting node
z1in standby mode, check the cluster status. Note that the resources should now all be running onz2.Copy to Clipboard Copied! Toggle word wrap Toggle overflow The web site at the defined IP address should still display, without interruption. - To remove
z1fromstandbymode, enter the following command.root@z1 ~]# pcs node unstandby z1.example.com
root@z1 ~]# pcs node unstandby z1.example.comCopy to Clipboard Copied! Toggle word wrap Toggle overflow Note
Removing a node fromstandbymode does not in itself cause the resources to fail back over to that node. This will depend on theresource-stickinessvalue for the resources. For information on theresource-stickinessmeta attribute, see Configuring a Resource to Prefer its Current Node in the Red Hat High Availability Add-On Reference.