Hi all,
Source code for the fourth (and very likely final) release candidate
for Pacemaker version 2.1.7 is available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.7-rc4
This release candidate fixes a newly found regression that was
introduced in rc1.
This is probably
On Tue, 2023-12-12 at 18:08 +0300, Artem wrote:
> Hi Andrei. pingd==0 won't satisfy both statements. It would if I used
> GTE, but I used GT.
> pingd lt 1 --> [0]
> pingd gt 0 --> [1,2,3,...]
It's the "or defined pingd" part of the rule that will match pingd==0.
A value of 0 is defined.
I'm
On Mon, 2023-12-11 at 21:05 +0300, Artem wrote:
> Hi Ken,
>
> On Mon, 11 Dec 2023 at 19:00, Ken Gaillot
> wrote:
> > > Question #2) I shut lustre3 VM down and leave it like that
> > How did you shut it down? Outside cluster control, or with
> > something
> > like pcs resource disable?
> >
>
>
On Tue, 2023-12-12 at 16:50 +0300, Artem wrote:
> Is there a detailed explanation for resource monitor and start
> timeouts and intervals with examples, for dummies?
No, though Pacemaker Explained has some reference information:
Hi Andrei. pingd==0 won't satisfy both statements. It would if I used GTE,
but I used GT.
pingd lt 1 --> [0]
pingd gt 0 --> [1,2,3,...]
On Tue, 12 Dec 2023 at 17:21, Andrei Borzenkov wrote:
> On Tue, Dec 12, 2023 at 4:47 PM Artem wrote:
> >> > pcs constraint location FAKE3 rule score=0 pingd
On Tue, Dec 12, 2023 at 4:47 PM Artem wrote:
>
>
>
> On Tue, 12 Dec 2023 at 16:17, Andrei Borzenkov wrote:
>>
>> On Fri, Dec 8, 2023 at 5:44 PM Artem 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
On Tue, Dec 12, 2023 at 4:50 PM Artem wrote:
>
> Is there a detailed explanation for resource monitor and start timeouts and
> intervals with examples, for dummies?
>
> my resource configured s follows:
> [root@lustre-mds1 ~]# pcs resource show MDT00
> Warning: This command is deprecated and
Is there a detailed explanation for resource monitor and start timeouts and
intervals with examples, for dummies?
my resource configured s follows:
[root@lustre-mds1 ~]# pcs resource show MDT00
Warning: This command is deprecated and will be removed. Please use 'pcs
resource config' instead.
On Tue, 12 Dec 2023 at 16:17, Andrei Borzenkov wrote:
> On Fri, Dec 8, 2023 at 5:44 PM Artem 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
On Fri, Dec 8, 2023 at 5:44 PM Artem wrote:
>
> Hello experts.
>
> I use pacemaker for a Lustre cluster. But for simplicity and exploration I
> use a Dummy resource. I didn't like how resource performed failover and
> failback. When I shut down VM with remote agent, pacemaker tries to restart
Dear Ken and other experts.
How can I leverage pingd to speedup failover? Or may be it is useless and
we should leverage monitor/start timeouts and
migration-threshold/failure-timeout ?
I have preference like this for normal operations:
> pcs constraint location FAKE3 prefers lustre3=100
> pcs
11 matches
Mail list logo
