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), so I
ended up doing individual (pcs cluster kill )
on each of the four cluster nodes. I then had
On 09/08/2016 03:55 PM, Scott Greenlese wrote:
>
> 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 '
1)M/S: POK 42HA/P966
From: Klaus Wenninger
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 questions for the group.
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 with
9:27 AM---On 09/08/2016 03:55 PM, Scott Greenlese
> wrote: >
>
> From: Klaus Wenninger
> To: users@clusterlabs.org
> Date: 09/08/2016 10:59 AM
> Subject: Re: [ClusterLabs] Pacemaker quorum behavior
>
>
&g
ct processes are not exiting on cluster kill or stop.
Thanks
Scott Greenlese ... IBM z/BX Solutions Test, Poughkeepsie, N.Y.
INTERNET: swgre...@us.ibm.com
PHONE: 8/293-7301 (845-433-7301)M/S: POK 42HA/P966
From: Jan Pokorný
To: Cluster Labs - All topics related to open-source clu
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 particu
0:59: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 Wenninger
>> To: users@clusterlabs.org
>> Date: 09/08/2016 10:59 AM
>
-433-7301) M/S: POK 42HA/P966
>>
>>
>> Inactive hide details for Klaus Wenninger ---09/08/2016 10:59:27
>> AM---On 09/08/2016 03:55 PM, Scott Greenlese wrote: >Klaus Wenninger
>> ---09/08/2016 10:59:27 A
8/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 my 5 node cluster, whe
28/2016 04:30:06 PM---Hi folks.. I have some follow-up
> questions about corosync daemon status after cluster shutdown.
>
> From: Scott Greenlese/Poughkeepsie/IBM
> To: kgail...@redhat.com, Cluster Labs - All topics related to
> open-source clustering welcomed
> Date: 09/28
er wrote: > On 09/08/201Ken Gaillot
---09/09/2016 06:23:37 PM---On 09/09/2016 04:27 AM, Klaus Wenninger
wrote: > On 09/08/2016 07:31 PM, Scott Greenlese wrote:
From: Ken Gaillot
To: users@clusterlabs.org
Date: 09/09/2016 06:23 PM
Subject: Re: [ClusterLabs] Pacemaker quorum behavior
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 p
13 matches
Mail list logo
