Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[doc] Issue in "Cluster bootstrap and more" #370

Open
ksanjeet opened this issue Mar 16, 2023 · 1 comment
Open

[doc] Issue in "Cluster bootstrap and more" #370

ksanjeet opened this issue Mar 16, 2023 · 1 comment

Comments

@ksanjeet
Copy link

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

@roseswe
Copy link

roseswe commented Apr 12, 2023

default_stickiness=$(crm_attribute -G -n resource-stickiness -t rsc_defaults -Q 2>/dev/null)

Throws this "error":

resource-stickiness=Multiple attributes match name=resource-stickiness
Value: 1000 (id=build-resource-stickiness)
Value: 1000 (id=rsc-options-resource-stickiness)

Also the question is with value is used by pacemaker to calculate his internal scores.....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants