You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to a recent update in pacemaker, "crm cluster init" automatically creates a default value of "resource-stickiness". Anyone wishing to update/overwrite this value can do so by:
But in our best practice guide, we are configuring a new value of this parameter with a different id. Using a different id creates a duplicate entry of this parameter and not overwrite as with above crm_attribute command. If we want to use a new id as in the best practice then the old entry of this parameter should be deleted(before configuring a new entry) using following command:
Cluster bootstrap and more:
https://documentation.suse.com/sbp/all/single-html/SLES4SAP-hana-sr-guide-PerfOpt-15/#id-cluster-bootstrap-and-more
Due to a recent update in pacemaker, "crm cluster init" automatically creates a default value of "resource-stickiness". Anyone wishing to update/overwrite this value can do so by:
crm_attribute -t rsc_defaults -n resource-stickiness -v <new_value>
But in our best practice guide, we are configuring a new value of this parameter with a different id. Using a different id creates a duplicate entry of this parameter and not overwrite as with above crm_attribute command. If we want to use a new id as in the best practice then the old entry of this parameter should be deleted(before configuring a new entry) using following command:
crm_attribute -t rsc_defaults -n resource-stickiness -D
The text was updated successfully, but these errors were encountered: