On 09/08/2016 06:33 PM, Digimer wrote:
> With 'fencing resource-and-stonith;' and a {un,}fence-handler set, DRBD
> will block when the peer is lost until the fence handler script returns
> indicating the peer was fenced/stonithed. In this way, the secondary
> WON'T promote to Primary while the
On 08/09/16 10:20 -0400, Scott Greenlese wrote:
> Correction...
>
> When I stopped pacemaker/corosync on the four (powered on / active)
> cluster node hosts, I was having an issue with the gentle method of
> stopping the cluster (pcs cluster stop --all),
Can you elaborate on what went wrong
Hi Klaus, thanks for your prompt and thoughtful feedback...
Please see my answers nested below (sections entitled, "Scott's Reply").
Thanks!
- Scott
Scott Greenlese ... IBM Solutions Test, Poughkeepsie, N.Y.
INTERNET: swgre...@us.ibm.com
PHONE: 8/293-7301 (845-433-7301)M/S: POK
Hi everyone,
I have a very basic question that I couldn't find an answer for.
I am using the pacemaker to control a 3 nodes cluster, with a private
application that works in an active - standby - standby mode.
My node have priorities in which is better to migrate to. I implemented it via
On 2016-09-08 02:03, Digimer wrote:
You need to solve the problem with fencing in DRBD. Leaving it off WILL
result in a split-brain eventually, full stop. With working fencing, you
will NOT get a split-brain, full stop.
"Split brain is a situation where, due to temporary failure of all
On 08/09/16 06:51 PM, Shermal Fernando wrote:
> Hi Jehan-Guillaume,
>
> Sorry for disturbing you. This is really important for us to pass this test
> on the pacemaker resiliency and robustness.
> To my understanding, it's the pacemakerd who feeds the watchdog. If only the
> crmd is hung,
Hi all...
I have a few very basic questions for the group.
I have a 5 node (Linux on Z LPARs) pacemaker cluster with 100 VirtualDomain
pacemaker-remote nodes
plus 100 "opaque" VirtualDomain resources. The cluster is configured to be
'symmetric' and I have no
location constraints on the 200
On 09/08/2016 02:28 PM, Ulrich Windl wrote:
Klaus Wenninger schrieb am 08.09.2016 um 09:13 in
> Nachricht <4c828344-44da-1d93-b43f-a305cfaa5...@redhat.com>:
>> On 09/08/2016 08:55 AM, Digimer wrote:
>>> On 08/09/16 03:47 PM, Ulrich Windl wrote:
>>> Shermal Fernando
>>> Klaus Wenninger schrieb am 08.09.2016 um 09:13 in
Nachricht <4c828344-44da-1d93-b43f-a305cfaa5...@redhat.com>:
> On 09/08/2016 08:55 AM, Digimer wrote:
>> On 08/09/16 03:47 PM, Ulrich Windl wrote:
>> Shermal Fernando schrieb am 08.09.2016
On Thu, 8 Sep 2016 09:51:27 +
Shermal Fernando wrote:
> Hi Jehan-Guillaume,
>
> Sorry for disturbing you. This is really important for us to pass this test
> on the pacemaker resiliency and robustness. To my understanding, it's the
> pacemakerd who feeds the
Hi Jehan-Guillaume,
Sorry for disturbing you. This is really important for us to pass this test on
the pacemaker resiliency and robustness.
To my understanding, it's the pacemakerd who feeds the watchdog. If only the
crmd is hung, fencing will not work. Am I correct here?
Regards,
Shermal
On 09/08/2016 10:58 AM, Shermal Fernando wrote:
> Hi Jehan-Guillaume,
>
> Does this means watchdog will serf-terminate the machine when the crm daemon
> is frozen?
Would be desirable but doesn't seem to happen - at least till now - will
see what I can do on that front.
>
> Regards,
> Shermal
Hi Jehan-Guillaume,
Does this means watchdog will serf-terminate the machine when the crm daemon is
frozen?
Regards,
Shermal Fernando
-Original Message-
From: Jehan-Guillaume de Rorthais [mailto:j...@dalibo.com]
Sent: Thursday, September 08, 2016 12:52 PM
To: Digimer
Cc:
On 09/08/2016 08:55 AM, Digimer wrote:
> On 08/09/16 03:47 PM, Ulrich Windl wrote:
> Shermal Fernando schrieb am 08.09.2016 um
> 06:41 in
>> Nachricht
>> <8ce6e8d87f896546b9c65ed80d30a4336578c...@lg-spmb-mbx02.lseg.stockex.local>:
>>> The whole cluster will
If the DC (crm daemon) is frozen (corosync is running without problem), DC will
not time out. Frozen DC will be there forever.
Regards,
Shermal Fernando
-Original Message-
From: Ulrich Windl [mailto:ulrich.wi...@rz.uni-regensburg.de]
Sent: Thursday, September 08, 2016 12:18 PM
> Thank you for the responses, I followed Digimer's instructions along with
> some information I had read on the DRBD site and configured fencing on the
> DRBD resource. I also configured STONITH using IPMI in Pacemaker. I setup
> Pacemaker first and verified that it kills the other node.
>
>
On 08/09/16 03:47 PM, Ulrich Windl wrote:
Shermal Fernando schrieb am 08.09.2016 um
06:41 in
> Nachricht
> <8ce6e8d87f896546b9c65ed80d30a4336578c...@lg-spmb-mbx02.lseg.stockex.local>:
>> The whole cluster will fail if the DC (crm daemon) is frozen due to CPU
>>> Shermal Fernando schrieb am 08.09.2016 um
>>> 06:41 in
Nachricht
<8ce6e8d87f896546b9c65ed80d30a4336578c...@lg-spmb-mbx02.lseg.stockex.local>:
> The whole cluster will fail if the DC (crm daemon) is frozen due to CPU
> starvation or hanging while trying to perform
Message: 1
Date: Wed, 7 Sep 2016 19:23:04 +0900
From: Digimer
To: Cluster Labs - All topics related to open-source clustering
welcomed
Subject: Re: [ClusterLabs] DRBD failover in Pacemaker
Message-ID:
19 matches
Mail list logo