roseswe / showscores

ShowScores - shows scores of pacemaker resources

Pacemaker ShowScores for SLES12 and SLES15

This program tries to show the scores each pacemaker resource has on cluster members (nodes).

See also the SUSE TID https://www.suse.com/support/kb/doc/?id=000019442 (no default-resource-stickiness)

NOTE: This program is not limited to two-node clusters (see examples below) like all the other scripts that I am aware of!

Motivation

In SLES12 and SLES15 commands and their output changed, so a new simplified showscores was invented! ✨

Original idea and script for older pacemaker versions (1.x) was done around 2009 by Dominik Klein. In the sub-directory SLES11 you will find a slightly enhanced and adapted version of Dominik original idea that runs only on SLES11 pacemaker clusters.

Requirements

This showscores version will not run under SLES11 because there the standard (G)AWK version is too old (GNU AWK 3.1.8) to support multidimensional arrays (please use instead the showscores version found in the SLES11 sub-directory). On the other hand SLES11 is meanwhile End-Of-Support/End-Of-Life (EoS/EoL).

It will run under SLES12SP5 = GNU AWK 4.1.8 (API: 1.0), SLES15SP2 = GNU AWK 4.1.0 (API: 1.0) and SLES15SP3/SP4/SP5 = GNU AWK 4.2.1 (API: 2.0)

Example Output SLES15, 2 node cluster

$ ./showscores
rsc_defaults: resource-stickiness=123   migration-threshold=5

## [ Resource ]#####[ Nodes -> ]##          sap12ha1           sap12ha2

admin-ip                                          0                123
c-clvm                                            0                  0
c-p_mail2sysadmin                                 0                  0
clee0                                             0                123
clem1                                           123                  0
dlm0                                              0                246
dlm1                                            246                  0
g-clvm0                                           0                  0
g-clvm1                                           0                  0
g-mariadb                                         0                  0
mariadb-ip                                      123                  0
p_mail2sysadmin0                                  0                123
p_mail2sysadmin1                                123                  0
p_mydummy                                       123                  0
prm_fs1                                           0                  0
prm_mariadb                                       0                  0
prm_vg1                                   -INFINITY          -INFINITY
stonith-sbd                                     123                  0

Example Output, SLES15, 3 Node SAP HANA SRA cluster, read-enable setup

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

##[ Resource ]#####[ Nodes ]##            hanode_02          hanode_mm          hanode_01

admin-ip                                       1000                  0                  0
cln_SAPHanaTopology_TST_HDB00                     0          -INFINITY                  0
msl_SAPHana_TST_HDB00                             2          -INFINITY                  2
rsc_SAPHanaTopology_TST_HDB000                    0          -INFINITY               1000
rsc_SAPHanaTopology_TST_HDB001                 1000          -INFINITY                  0
rsc_SAPHanaTopology_TST_HDB002                    0          -INFINITY                  0
rsc_SAPHana_TST_HDB000                            2          -INFINITY               1152
rsc_SAPHana_TST_HDB001                         1102          -INFINITY                  0
rsc_ip_TST_HDB00_master                           0          -INFINITY               3000
rsc_ip_TST_HDB00_readenabled                   3000          -INFINITY                  0

Showscore taken on node: hanode_mm at Wed Apr 12 12:13:08 CEST 2023

NOTE: hanode_mm is the "Majority Maker" node and the rsc_defaults output is affected by "Bug 1210614 - Duplicated entries for resource-stickiness"

Example Output SLES15, 3 Node SAP HANA SRA cluster, read-enable setup - wrong stickiness/threshold

rsc_defaults: resource-stickiness=1   migration-threshold=3


##[ Resource ]#####[ Nodes ]##       majority-maker              node01             node02

admin-ip                                          0                  1                  0
cln_SAPHanaTopology_R44_HDB00             -INFINITY                  0                  0
msl_SAPHana_R44_HDB00                     -INFINITY                  1                  1
rsc_SAPHanaTopology_R44_HDB000            -INFINITY                  1                  0
rsc_SAPHanaTopology_R44_HDB001            -INFINITY                  0                  1
rsc_SAPHanaTopology_R44_HDB002            -INFINITY                  0                  0
rsc_SAPHana_R44_HDB000                    -INFINITY                152                  1
rsc_SAPHana_R44_HDB001                    -INFINITY                  0                102
rsc_ip_R44_HDB00_master                   -INFINITY               2001                  0
rsc_ip_R44_HDB00_readenabled              -INFINITY                  0               2001

Example Output SLES15, 3 Node SAP HANA SRA cluster, read-enable setup - stickiness/threshold according to SUSE Best Practices

rsc_defaults: resource-stickiness=1000   migration-threshold=5000

##[ Resource ]#####[ Nodes -> ]##    majority-maker             node01             node02

cln_SAPHanaTopology_R44_HDB00             -INFINITY                  0                  0
msl_SAPHana_R44_HDB00                     -INFINITY                  2                  2
rsc_SAPHanaTopology_R44_HDB000            -INFINITY               1000                  0
rsc_SAPHanaTopology_R44_HDB001            -INFINITY                  0               1000
rsc_SAPHanaTopology_R44_HDB002            -INFINITY                  0                  0
rsc_SAPHana_R44_HDB000                    -INFINITY               1152                  2
rsc_SAPHana_R44_HDB001                    -INFINITY                  0               1102
rsc_admin-ip                                      0               1000                  0
rsc_ip_R44_HDB00_master                   -INFINITY               3000                  0
rsc_ip_R44_HDB00_readenabled              -INFINITY                  0               3000

end of documentation....

showscores's Issues

add code handling errors or stopped cluster services

showscores/showscores

Line 23 in ec4d631

## TODO: Stop here if an error is raised -> cluster framework not running (e.g. crm cluster stop)

Script works OK here, but could be better (error) handled

resource-stickiness=Multiple attributes match --

Fix to correct output

cat CIB:

rsc_defaults build-resource-defaults:
resource-stickiness=1

rsc_defaults rsc-options:
resource-stickiness=1000
migration-threshold=5000

TODO: Maybe replace in the tr command ":" with "_" for better readability?

showscores/showscores

Line 28 in ec4d631

## TODO: Maybe replace in the tr command ":" with "_" for better readability?

gitlab: Actions - fix YAML file showscores/.github/workflows/shellcheck.yml

Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: actions/checkout@v2

test with multi-node clusters (3+)

Should work with multi-node cluster due to dynamic AWK arrays