Re: [ClusterLabs] Antw: Re: questions about startup fencing

04.12.2017 18:47, Tomas Jelinek пишет: > Dne 4.12.2017 v 16:02 Kristoffer Grönlund napsal(a): >> Tomas Jelinek writes: >> * how is it shutting down the cluster when issuing "pcs cluster stop --all"? >>> >>> First, it sends a request to each node to stop

Re: [ClusterLabs] pcs create master/slave resource doesn't work (Ken Gaillot)

On Mon, 2017-12-04 at 23:15 +0800, Hui Xiang wrote: > Thanks Ken very much for the helpful information. It indeed help a > lot for debbuging. > >  " Each time the DC decides what to do, there will be a line like > "... > saving inputs in ..." with a file name. The log messages just before > that

[ClusterLabs] Pacemaker/Corosync on FreeBSD

Hi guys, I few times in the past, I had the need to work with Pacemaker clusters. Always on Linux (CentOS or Debian). However, I'm biased to FreeBSD, so a couple weeks ago I wanted to try Pacemaker on FreeBSD for the first time. I found packages in official FreeBSD repos for pacemaker, corosync

Re: [ClusterLabs] pacemaker with sbd fails to start if node reboots too fast.

04.12.2017 14:48, Gao,Yan пишет: > On 12/02/2017 07:19 PM, Andrei Borzenkov wrote: >> 30.11.2017 13:48, Gao,Yan пишет: >>> On 11/22/2017 08:01 PM, Andrei Borzenkov wrote: SLES12 SP2 with pacemaker 1.1.15-21.1-e174ec8; two node cluster with VM on VSphere using shared VMDK as SBD. During

Re: [ClusterLabs] Pacemaker/Corosync on FreeBSD

Hello Alberto, On 04/12/17 16:12 -0400, Alberto Mijares wrote: > At this point, I need to know if someone is using pacemaker/corosync > on FreeBSD. Is it a problem with crmsh only? well, it's enough to have a look at which people develop these high level tooling (crm, pcs) and you'll figure out

Re: [ClusterLabs] Antw: Re: questions about startup fencing

On Mon, 2017-12-04 at 22:08 +0300, Andrei Borzenkov wrote: > 04.12.2017 18:47, Tomas Jelinek пишет: > > Dne 4.12.2017 v 16:02 Kristoffer Grönlund napsal(a): > > > Tomas Jelinek writes: > > > > > > > > > > > > > * how is it shutting down the cluster when issuing "pcs > > > >

Re: [ClusterLabs] Antw: Re: Regression in Filesystem RA

Hello, On Thu, 30 Nov 2017 09:41:00 +0100 Ulrich Windl wrote: > > Hello, > > > > sorry for the late reply, moving Date Centers tends to keep one busy. > > > > I looked at the PR and while it works and certainly is an improvement, it > > wouldn't help me in my case much. > > Biggest issue

Re: [ClusterLabs] Pacemaker/Corosync on FreeBSD

On Mon, Dec 4, 2017 at 6:53 PM, Jan Pokorný wrote: > Hello Alberto, > Hello Jan, Thanks for your feedback. > On 04/12/17 16:12 -0400, Alberto Mijares wrote: >> At this point, I need to know if someone is using pacemaker/corosync >> on FreeBSD. Is it a problem with crmsh

Re: [ClusterLabs] Antw: Re: questions about startup fencing

On Fri, 01 Dec 2017 16:34:08 -0600 Ken Gaillot wrote: > On Thu, 2017-11-30 at 07:55 +0100, Ulrich Windl wrote: > > > > > > > Kristoffer Gronlund wrote: > > > > Adam Spiers writes: > > > > > > > > > - The whole cluster is shut

[ClusterLabs] Corosync and pacemaker token thresholds with Juniper CoS

Hello, I was hoping someone could explain the use of thresholds in communication between HA/Cluster members, more specifically their use of ping and latency. We have noticed issues with ICMP latency gathering in other services and hardware and are wondering if this could be the case with the

Re: [ClusterLabs] Antw: Re: pacemaker with sbd fails to start if node reboots too fast.

On 12/02/2017 08:30 AM, Andrei Borzenkov wrote: 01.12.2017 22:36, Gao,Yan пишет: On 11/30/2017 06:48 PM, Andrei Borzenkov wrote: 30.11.2017 16:11, Klaus Wenninger пишет: On 11/30/2017 01:41 PM, Ulrich Windl wrote: "Gao,Yan" schrieb am 30.11.2017 um 11:48 in Nachricht

Re: [ClusterLabs] pacemaker with sbd fails to start if node reboots too fast.

On 12/02/2017 07:19 PM, Andrei Borzenkov wrote: 30.11.2017 13:48, Gao,Yan пишет: On 11/22/2017 08:01 PM, Andrei Borzenkov wrote: SLES12 SP2 with pacemaker 1.1.15-21.1-e174ec8; two node cluster with VM on VSphere using shared VMDK as SBD. During basic tests by killing corosync and forcing

Re: [ClusterLabs] Antw: Re: questions about startup fencing

On Mon, 4 Dec 2017 12:31:06 +0100 Tomas Jelinek wrote: > Dne 4.12.2017 v 10:36 Jehan-Guillaume de Rorthais napsal(a): > > On Fri, 01 Dec 2017 16:34:08 -0600 > > Ken Gaillot wrote: > > > >> On Thu, 2017-11-30 at 07:55 +0100, Ulrich Windl wrote: >

Re: [ClusterLabs] Antw: Re: questions about startup fencing

Tomas Jelinek writes: >> >> * how is it shutting down the cluster when issuing "pcs cluster stop --all"? > > First, it sends a request to each node to stop pacemaker. The requests > are sent in parallel which prevents resources from being moved from node > to node. Once

Re: [ClusterLabs] Antw: Re: questions about startup fencing

On 12/04/2017 04:02 PM, Kristoffer Grönlund wrote: > Tomas Jelinek writes: > >>> * how is it shutting down the cluster when issuing "pcs cluster stop --all"? >> First, it sends a request to each node to stop pacemaker. The requests >> are sent in parallel which prevents

Re: [ClusterLabs] pcs create master/slave resource doesn't work (Ken Gaillot)

Thanks Ken very much for the helpful information. It indeed help a lot for debbuging. " Each time the DC decides what to do, there will be a line like "... saving inputs in ..." with a file name. The log messages just before that may give some useful information." - I am unable to find such

Re: [ClusterLabs] Antw: Re: questions about startup fencing

Dne 4.12.2017 v 16:02 Kristoffer Grönlund napsal(a): Tomas Jelinek writes: * how is it shutting down the cluster when issuing "pcs cluster stop --all"? First, it sends a request to each node to stop pacemaker. The requests are sent in parallel which prevents resources

Re: [ClusterLabs] Antw: Re: questions about startup fencing

Dne 4.12.2017 v 14:21 Jehan-Guillaume de Rorthais napsal(a): On Mon, 4 Dec 2017 12:31:06 +0100 Tomas Jelinek wrote: Dne 4.12.2017 v 10:36 Jehan-Guillaume de Rorthais napsal(a): On Fri, 01 Dec 2017 16:34:08 -0600 Ken Gaillot wrote: On Thu,

Re: [ClusterLabs] Adding Tomcat as a resource to a Cluster on CentOS 7

Thank you for the replay, Oyvind. I gave it plenty of time to start up. using tomcat_name="tomcat" it starts what I can only call a lifeless PID, but it never seems to actually start up. The catalina.out file is never touched, so it never has anything in it to indicate a problem. Pacemaker does