Difference between revisions of "CRM cluster on Suse Miscellaneous notes"
From Notes_Wiki
(Created page with "Home > Suse > SAP setup and maintenance > CRM cluster on Suse Miscellaneous notes =Accessing cluster via web interface= Access cluster via https://<hostname-or-ip>:7630/ (Hawk) and login via appropriate user such as hacluster.") |
m |
||
(One intermediate revision by the same user not shown) | |||
Line 3: | Line 3: | ||
=Accessing cluster via web interface= | =Accessing cluster via web interface= | ||
Access cluster via https://<hostname-or-ip>:7630/ (Hawk) and login via appropriate user such as hacluster. | Access cluster via https://<hostname-or-ip>:7630/ (Hawk) and login via appropriate user such as hacluster. | ||
=Avoid moving resources without timeout= | |||
If we move a resource to / from a node then it creates a permanent location constraint for affinity / anti-affinity based on move command similar to: | |||
<pre> | |||
location cli-prefer-grp_ASCS grp_ASCS role=Started inf: EXAPRI1 | |||
</pre> | |||
These create problem when we no longer need a particular resource on a specific machine. | |||
Thus if you iniitally move a resource using: | |||
<pre> | |||
crm resource migrate r0 node2 | |||
</pre> | |||
then once task is complete use: | |||
<pre> | |||
crm resource unmigrate r0 | |||
</pre> | |||
to remove the cli-prefer constraint. | |||
Other option is to manually edit configuration and remove the location constraint from the configuration. | |||
Refer: | |||
* https://unix.stackexchange.com/questions/170986/pacemaker-migrate-resource-without-adding-a-prefer-line-in-config | |||
[[Main Page|Home]] > [[Suse]] > [[SAP setup and maintenance]] > [[CRM cluster on Suse Miscellaneous notes]] |
Latest revision as of 07:35, 11 June 2023
Home > Suse > SAP setup and maintenance > CRM cluster on Suse Miscellaneous notes
Accessing cluster via web interface
Access cluster via https://<hostname-or-ip>:7630/ (Hawk) and login via appropriate user such as hacluster.
Avoid moving resources without timeout
If we move a resource to / from a node then it creates a permanent location constraint for affinity / anti-affinity based on move command similar to:
location cli-prefer-grp_ASCS grp_ASCS role=Started inf: EXAPRI1
These create problem when we no longer need a particular resource on a specific machine.
Thus if you iniitally move a resource using:
crm resource migrate r0 node2
then once task is complete use:
crm resource unmigrate r0
to remove the cli-prefer constraint.
Other option is to manually edit configuration and remove the location constraint from the configuration.
Refer:
Home > Suse > SAP setup and maintenance > CRM cluster on Suse Miscellaneous notes