[ClusterLabs] ocf:pacemaker:ping works strange
Artem
tyomikh at gmail.com
Tue Dec 12 08:46:50 EST 2023
On Tue, 12 Dec 2023 at 16:17, Andrei Borzenkov <arvidjaar at gmail.com> wrote:
> On Fri, Dec 8, 2023 at 5:44 PM Artem <tyomikh at gmail.com> wrote:
> > pcs constraint location FAKE3 rule score=0 pingd lt 1 or not_defined
> pingd
> > pcs constraint location FAKE4 rule score=0 pingd lt 1 or not_defined
> pingd
> > pcs constraint location FAKE3 rule score=125 pingd gt 0 or defined pingd
> > pcs constraint location FAKE4 rule score=125 pingd gt 0 or defined pingd
> >
>
> These rules are contradicting. You set the score to 125 if pingd is
> defined and at the same time set it to 0 if the score is less than 1.
> To be "less than 1" it must be defined to start with so both rules
> will always apply. I do not know how the rules are ordered. Either you
> get random behavior, or one pair of these rules is effectively
> ignored.
>
"pingd lt 1 or not_defined pingd" means to me ==0 or not_defined, that is
ping fails to ping GW or fails to report to corosync/pacemaker. Am I wrong?
"pingd gt 0 or defined pingd" means to me that ping gets reply from GW and
reports it to cluster.
Are they really contradicting?
I read this article and tried to do in a similar way:
https://habr.com/ru/articles/118925/
>
> > Question #1) Why I cannot see accumulated score from pingd in
> crm_simulate output? Only location score and stickiness.
> > pcmk__primitive_assign: FAKE3 allocation score on lustre3: 210
> > pcmk__primitive_assign: FAKE3 allocation score on lustre4: 90
> > pcmk__primitive_assign: FAKE4 allocation score on lustre3: 90
> > pcmk__primitive_assign: FAKE4 allocation score on lustre4: 210
> > Either when all is OK or when VM is down - score from pingd not added to
> total score of RA
> >
> >
> > Question #2) I shut lustre3 VM down and leave it like that. pcs status:
> > * FAKE3 (ocf::pacemaker:Dummy): Stopped
> > * FAKE4 (ocf::pacemaker:Dummy): Started lustre4
> > * Clone Set: ping-clone [ping]:
> > * Started: [ lustre-mds1 lustre-mds2 lustre-mgs lustre1 lustre2
> lustre4 ] << lustre3 missing
> > OK for now
> > VM boots up. pcs status:
> > * FAKE3 (ocf::pacemaker:Dummy): FAILED (blocked) [ lustre3
> lustre4 ] << what is it?
> > * Clone Set: ping-clone [ping]:
> > * ping (ocf::pacemaker:ping): FAILED lustre3 (blocked) <<
> why not started?
> > * Started: [ lustre-mds1 lustre-mds2 lustre-mgs lustre1 lustre2
> lustre4 ]
>
> If this is full pcs status output, I miss stonith resource.
>
> I have "pcs property set stonith-enabled=false" and don't plan to use it.
I want simple active-passive cluster, like Veritas or ServiceGuard with
most duties automated. And our production servers have their iBMC in a
locked network segment
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20231212/5ada8b7b/attachment-0001.htm>
More information about the Users
mailing list