On 28/09/16 16:30 -0400, Scott Greenlese wrote:
> Also, I have tried simulating a failed cluster node (to trigger a
> STONITH action) by killing the corosync daemon on one node, but all
> that does is respawn the daemon ... causing a temporary / transient
> failure condition, and no fence takes
.org>
Date: 09/28/2016 04:30 PM
Subject: Re: [ClusterLabs] Pacemaker quorum behavior
Hi folks..
I have some follow-up questions about corosync daemon status after
cluster shutdown.
Basically, what should happen to corosyn
abs.org>
Date: 09/28/2016 04:30 PM
Subject:Re: [ClusterLabs] Pacemaker quorum behavior
Hi folks..
I have some follow-up questions about corosync daemon status after cluster
shutdown.
Basically, what should happen to corosync on a cluster node when pacemaker
is shutdown on that node?
On m
o: users@clusterlabs.org
Date: 09/09/2016 06:23 PM
Subject:Re: [ClusterLabs] Pacemaker quorum behavior
On 09/09/2016 04:27 AM, Klaus Wenninger wrote:
> On 09/08/2016 07:31 PM, Scott Greenlese wrote:
>>
>> Hi Klaus, thanks for your prompt and thoughtful feedback...
>>
27
>> AM---On 09/08/2016 03:55 PM, Scott Greenlese wrote: >Klaus Wenninger
>> ---09/08/2016 10:59:27 AM---On 09/08/2016 03:55 PM, Scott Greenlese
>> wrote: >
>>
>> From: Klaus Wennin
On 09/09/16 14:13 -0400, Scott Greenlese wrote:
> You had mentioned this command:
>
> pstree -p | grep -A5 $(pidof -x pcs)
>
> I'm not quite sure what the $(pidof -x pcs) represents??
This is a "command substitution" shell construct (new, blessed form
of `backtick` notation) that in this
;
Cc: Si Bo Niu <nius...@cn.ibm.com>, Scott
Loveland/Poughkeepsie/IBM@IBMUS, Michael
Tebolt/Poughkeepsie/IBM@IBMUS
Date: 09/08/2016 02:43 PM
Subject:Re: [ClusterLabs] Pacemaker quorum behavior
On 08/09/16 10:20 -0400, Scott Greenlese wrote:
> Co
AM---On 09/08/2016 03:55 PM, Scott Greenlese
> wrote: >
>
> From: Klaus Wenninger <kwenn...@redhat.com>
> To: users@clusterlabs.org
> Date: 09/08/2016 10:59 AM
> Subject: Re: [ClusterLabs] Pacemaker quorum behavior
>
> -
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
M/S: POK 42HA/P966
From: Klaus Wenninger <kwenn...@redhat.com>
To: users@clusterlabs.org
Date: 09/08/2016 10:59 AM
Subject:Re: [ClusterLabs] Pacemaker quorum behavior
On 09/08/2016 03:55 PM, Scott Greenlese wrote:
>
> Hi all...
>
> I have a few very basic qu
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
11 matches
Mail list logo
