Fencing could work. Thanks again Reid.
From: Users on behalf of Reid Wahl
Sent: 23 July 2020 10:10
To: Cluster Labs - All topics related to open-source clustering welcomed
Subject: EXTERNAL: Re: [ClusterLabs] Pacemaker Shutdown
Thanks for the clarification.
Thanks for the clarification. As far as I'm aware, there's no way to do
this at the Pacemaker level during a Pacemaker shutdown. It would require
uncleanly killing all resources, which doesn't make sense at the Pacemaker
level.
Pacemaker only knows how to stop a resource by running the resource
Thanks for your response Reid. What you say makes sense, and under normal
circumstances if a resource failed, I'd want all of its dependents to be
stopped cleanly before restarting the failed resource. However if pacemaker is
shutting down on a node (e.g. due to a restart request), then I just
On Tue, Jul 21, 2020 at 11:42 PM Harvey Shepherd <
harvey.sheph...@aviatnet.com> wrote:
> Hi All,
>
> I'm running Pacemaker 2.0.3 on a two-node cluster, controlling 40+
> resources which are a mixture of clones and other resources that are
> colocated with the master instance of certain clones.
On Wed, 2020-07-22 at 17:04 +0300, Andrei Borzenkov wrote:
>
>
> On Wed, Jul 22, 2020 at 4:58 PM Ken Gaillot
> wrote:
> > On Wed, 2020-07-22 at 10:59 +0300, Хиль Эдуард wrote:
> > > Hi there! I have 2 nodes with Pacemaker 2.0.3, corosync 3.0.3 on
> > > ubuntu 20 + 1 qdevice. I want to define
On Wed, Jul 22, 2020 at 10:57 AM Andrei Borzenkov
wrote:
> 22.07.2020 12:46, Хиль Эдуард пишет:
> >
> > Hey, Andrei! Thanx for ur time!
> > A-a-and there is no chance to do something? :(
> > The pacemaker’s log below.
> >
>
> Resource was started:
>
> ...
> > Jul 22 12:38:36 node2.local
22.07.2020 12:46, Хиль Эдуард пишет:
>
> Hey, Andrei! Thanx for ur time!
> A-a-and there is no chance to do something? :(
> The pacemaker’s log below.
>
Resource was started:
...
> Jul 22 12:38:36 node2.local pacemaker-execd [1721] (log_execute)
> info: executing - rsc:dummy.service
On Wed, Jul 22, 2020 at 4:58 PM Ken Gaillot wrote:
> On Wed, 2020-07-22 at 10:59 +0300, Хиль Эдуард wrote:
> > Hi there! I have 2 nodes with Pacemaker 2.0.3, corosync 3.0.3 on
> > ubuntu 20 + 1 qdevice. I want to define new resource as systemd
> > unit dummy.service :
> >
> > [Unit]
> >
On Wed, 2020-07-22 at 10:59 +0300, Хиль Эдуард wrote:
> Hi there! I have 2 nodes with Pacemaker 2.0.3, corosync 3.0.3 on
> ubuntu 20 + 1 qdevice. I want to define new resource as systemd
> unit dummy.service :
>
> [Unit]
> Description=Dummy
> [Service]
> Restart=on-failure
>
Hey, Andrei! Thanx for ur time!
A-a-and there is no chance to do something? :(
The pacemaker’s log below.
Jul 22 12:38:36 node2.local pacemaker-based [1719] (cib_process_request)
info: Forwarding cib_apply_diff operation for section 'all' to all
(origin=local/cibadmin/2)
Jul 22
Hi Klaus! Thank you for your attention, but isn’t work. I have added
Type=simple and there is no changes. I think problem not in service. As we can
see from logs, the service is starting (Jul 21 15:53:42 node2.local
dummy[9330]: hello world 1) but for the some reason pacemaker isn’t see it
Hi there! I have 2 nodes with Pacemaker 2.0.3, corosync 3.0.3 on ubuntu 20 + 1
qdevice. I want to define new resource as systemd unit dummy.service :
[Unit]
Description=Dummy
[Service]
Restart=on-failure
StartLimitInterval=20
StartLimitBurst=5
TimeoutStartSec=0
RestartSec=5
On Wed, Jul 22, 2020 at 10:59 AM Хиль Эдуард wrote:
> Hi there! I have 2 nodes with Pacemaker 2.0.3, corosync 3.0.3 on ubuntu 20
> + 1 qdevice. I want to define new resource as systemd unit *dummy.service
> *:
>
> [Unit]
> Description=Dummy
> [Service]
> Restart=on-failure
>
On Wed, Jul 22, 2020 at 9:42 AM Harvey Shepherd <
harvey.sheph...@aviatnet.com> wrote:
> Hi All,
>
> I'm running Pacemaker 2.0.3 on a two-node cluster, controlling 40+
> resources which are a mixture of clones and other resources that are
> colocated with the master instance of certain clones.
On 7/22/20 9:59 AM, Хиль Эдуард wrote:
> Hi there! I have 2 nodes with Pacemaker 2.0.3, corosync 3.0.3 on
> ubuntu 20 + 1 qdevice. I want to define new resource as systemd
> unit *dummy.service *:
>
> [Unit]
> Description=Dummy
> [Service]
Type=simple
That could do the trick. Actually I thought
Hi All,
I'm running Pacemaker 2.0.3 on a two-node cluster, controlling 40+ resources
which are a mixture of clones and other resources that are colocated with the
master instance of certain clones. I've noticed that if I terminate pacemaker
on the node that is hosting the master instances of
16 matches
Mail list logo
