14.11.2014 17:36, David Vossel пишет:
>
>
> - Original Message -
>> Hi!
>>
>> Just noticed that deletion of a trace_ra op attribute forces resource
>> to be restarted (that RA does not support reload).
>>
>> Logs show:
>> Nov 13 09:06:05 [6633] node01cib: info: cib_process_req
We are running the following versions:
crmsh 1.2.6
pacemaker 1.1.10
corosync 1.4.1
On 11/14/14 9:28 AM, "Dejan Muhamedagic" wrote:
>Hi,
>
>On Thu, Nov 13, 2014 at 06:52:29PM +, Scott Donoho wrote:
>> Here is a simple Active/Passive configuration with a single Dummy
>>resource (see end of
Hello all
we are trying to have in a 2 node cluster one resource TEST (LSB type)
cloned but we woul like to have it running in the 2 nodes and be able to
stop and start it on each independently
then we would like to associate to it some virtual iP type OCF using a
location or something like that
Hi,
On Thu, Nov 13, 2014 at 06:52:29PM +, Scott Donoho wrote:
> Here is a simple Active/Passive configuration with a single Dummy resource
> (see end of message). The resource-stickiness default is set to 100. I was
> assuming that this would be enough to keep the Dummy resource on the activ
- Original Message -
> Hi!
>
> Just noticed that deletion of a trace_ra op attribute forces resource
> to be restarted (that RA does not support reload).
>
> Logs show:
> Nov 13 09:06:05 [6633] node01cib: info: cib_process_request:
> Forwarding cib_apply_diff operation for s
Please find attached.
Kind regards,
Dmitriy Matveichev.
-Original Message-
From: Andrei Borzenkov [mailto:arvidj...@gmail.com]
Sent: Friday, November 14, 2014 4:44 PM
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] Long failover
On Fri, No
- Original Message -
> Here is a simple Active/Passive configuration with a single Dummy resource
> (see end of message). The resource-stickiness default is set to 100. I was
> assuming that this would be enough to keep the Dummy resource on the active
> node as long as the active node st
On Fri, Nov 14, 2014 at 4:33 PM, Dmitry Matveichev
wrote:
> We've already tried to set it but it didn't help.
>
I doubt it is possible to say anything without logs.
>
> Kind regards,
> Dmitriy Matveichev.
>
>
> -Original Message-
> From: Andrei Borzenkov [mailto:
We've already tried to set it but it didn't help.
Kind regards,
Dmitriy Matveichev.
-Original Message-
From: Andrei Borzenkov [mailto:arvidj...@gmail.com]
Sent: Friday, November 14, 2014 4:12 PM
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemake
On Fri, Nov 14, 2014 at 2:57 PM, Dmitry Matveichev
wrote:
> Hello,
>
>
>
> We have a cluster configured via pacemaker+corosync+crm. The configuration
> is:
>
>
>
> node master
>
> node slave
>
> primitive HA-VIP1 IPaddr2 \
>
> params ip=192.168.22.71 nic=bond0 \
>
> op monitor inte
you need to configure the fencing in pacemaker
2014-11-14 13:04 GMT+01:00 Heiner Meier :
> Hello,
>
> i now have configured fencing in drbd:
>
> disk {
> fencing resource-only;
> }
> handlers {
> fence-peer "/usr/lib/drbd/crm-fence-peer.sh";
Hello,
i now have configured fencing in drbd:
disk {
fencing resource-only;
}
handlers {
fence-peer "/usr/lib/drbd/crm-fence-peer.sh";
after-resync-target "/usr/lib/drbd/crm-unfence-peer.sh";
}
And changed the config
Hello,
We have a cluster configured via pacemaker+corosync+crm. The configuration is:
node master
node slave
primitive HA-VIP1 IPaddr2 \
params ip=192.168.22.71 nic=bond0 \
op monitor interval=1s
primitive HA-variator lsb: variator \
op monitor interval=1s \
meta m
On 14/11/14 11:01, Daniel Dehennin wrote:
Christine Caulfield writes:
[...]
If its only happening at startup it could be the switch/router
learning the ports for the nodes and building its routing
tables. Switching to udpu will then get rid of the message if it's
annoying
Switching to updu
Christine Caulfield writes:
[...]
> If its only happening at startup it could be the switch/router
> learning the ports for the nodes and building its routing
> tables. Switching to udpu will then get rid of the message if it's
> annoying
Switching to updu make it works correctly.
Thanks.
--
Christine Caulfield writes:
[...]
> If its only happening at startup it could be the switch/router
> learning the ports for the nodes and building its routing
> tables. Switching to udpu will then get rid of the message if it's
> annoying
When I start the corosync process of the VM, nothing ha
On 13/11/14 17:54, Daniel Dehennin wrote:
Digimer writes:
This generally happens if the network is slow or congested. It is
corosync saying it needs to resend some messages. It is not uncommon
for it to happen now and then, but that is a fairly large amount of
retransmits.
Thanks for the exp
I am very happy that I somehow triggered this discussion :).
What I did was basically just take the information that was available to me
(thanks to Andreas notes and mainly his previous patches that he sent over
the years) and provide a single place where one could look at and get
pacemaker runnin
18 matches
Mail list logo
