[ClusterLabs] expected_votes in cluster conf

[Reid Wahl]

On Sun, Oct 9, 2022 at 7:10 AM Lentes, Bernd
<bernd.lentes at helmholtz-muenchen.de> wrote:
>
> Dear all,
>
> while checking my cluster with "crm status xml" i stumbled across:
> ha-idg-1:/usr/lib/ocf/resource.d/heartbeat # crm status xml
> <?xml version="1.0"?>
> <crm_mon version="1.1.24">
>     <summary>
>         <stack type="corosync" />
>         <current_dc present="true" version="1.1.24+20210811.f5abda0ee-3.21.9-1.1.24+20210811.f5abda0ee" name="ha-idg-1" id="1084777482" with_quorum="true" />
>         <last_update time="Sun Oct  9 15:21:26 2022" />
>         <last_change time="Sun Oct  9 15:04:03 2022" user="root" client="cibadmin" origin="ha-idg-1" />
>
>         <nodes_configured number="2" expected_votes="unknown" />   <=========================================
>
>         <resources_configured number="40" disabled="6" blocked="0" />
>         <cluster_options stonith-enabled="true" symmetric-cluster="true" no-quorum-policy="ignore" maintenance-mode="false" />
>     </summary>
>
> expected_votes="unknown" ?
> I didn't find expected_votes in the pacemaker doc (https://clusterlabs.org/pacemaker/doc/deprecated/en-US/Pacemaker/1.1/html-single/Pacemaker_Explained/index.html).
> It's a setting for corosync.conf and in mine it is:
> expected_votes: 2. I have a two-node cluster.
>
> I don't know from where "expected_votes="unknown"" comes in my case, maybe a typo.
> Can you confirm that it isn't an option for pacemaker conf ? Or maybe an undocumentated ?

Hi, Bernd. That field is related to corosync membership and was
removed in 2.0.0 when support for corosync v1 was removed:
https://github.com/ClusterLabs/pacemaker/commit/7a9891f

It's still present in 1.1.24. As you can see, crm_mon looks for an
nvpair in the CIB with name="expected-quorum-votes" and uses that
value if found, otherwise "unknown":
https://github.com/ClusterLabs/pacemaker/blob/Pacemaker-1.1.24/tools/crm_mon.c#L2601-L2692

I'm not sure exactly how it was supposed to get set... it looks like
crmd/corosync.c:crmd_cs_dispatch() would set it on the DC for a
crm_class_members or crm_class_quorum message, but not sure what
sequence of events would lead that to happen in some cases and not in
your case.

>
> Thanks.
>
> Bernd
>
>
> --
> Bernd Lentes
> System Administrator
> Institute for Metabolism and Cell Death (MCD)
> Building 25 - office 122
> HelmholtzZentrum München
> bernd.lentes at helmholtz-muenchen.de
> phone: +49 89 3187 1241
>        +49 89 3187 49123
> fax:   +49 89 3187 2294
> https://www.helmholtz-munich.de/en/mcd
>
> Public key:
> 30 82 01 0a 02 82 01 01 00 b3 72 3e ce 2c 0a 6f 58 49 2c 92 23 c7 b9 c1 ff 6c 3a 53 be f7 9e e9 24 b7 49 fa 3c e8 de 28 85 2c d3 ed f7 70 03 3f 4d 82 fc cc 96 4f 18 27 1f df 25 b3 13 00 db 4b 1d ec 7f 1b cf f9 cd e8 5b 1f 11 b3 a7 48 f8 c8 37 ed 41 ff 18 9f d7 83 51 a9 bd 86 c2 32 b3 d6 2d 77 ff 32 83 92 67 9e ae ae 9c 99 ce 42 27 6f bf d8 c2 a1 54 fd 2b 6b 12 65 0e 8a 79 56 be 53 89 70 51 02 6a eb 76 b8 92 25 2d 88 aa 57 08 42 ef 57 fb fe 00 71 8e 90 ef b2 e3 22 f3 34 4f 7b f1 c4 b1 7c 2f 1d 6f bd c8 a6 a1 1f 25 f3 e4 4b 6a 23 d3 d2 fa 27 ae 97 80 a3 f0 5a c4 50 4a 45 e3 45 4d 82 9f 8b 87 90 d0 f9 92 2d a7 d2 67 53 e6 ae 1e 72 3e e9 e0 c9 d3 1c 23 e0 75 78 4a 45 60 94 f8 e3 03 0b 09 85 08 d0 6c f3 ff ce fa 50 25 d9 da 81 7b 2a dc 9e 28 8b 83 04 b4 0a 9f 37 b8 ac 58 f1 38 43 0e 72 af 02 03 01 00 01
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/



-- 
Regards,

Reid Wahl (He/Him)
Senior Software Engineer, Red Hat
RHEL High Availability - Pacemaker