Re: [ClusterLabs] Questions about SBD behavior

2018-06-25 Thread Klaus Wenninger
nce races are going to avoid with delay attribute: >>> https://access.redhat.com/solutions/91653 >>> https://access.redhat.com/solutions/1293523) >> I'm not sure if I get your point here. >> Watchdog-fencing on a 2-node-cluster without >> additional qdevice or shared

Re: [ClusterLabs] Questions about SBD behavior

2018-06-25 Thread 井上 和徳
> -Original Message- > From: Klaus Wenninger [mailto:kwenn...@redhat.com] > Sent: Wednesday, June 13, 2018 6:40 PM > To: Cluster Labs - All topics related to open-source clustering welcomed; 井上 和 > 徳 > Subject: Re: [ClusterLabs] Questions about SBD behavior > > On

Re: [ClusterLabs] Questions about SBD behavior

2018-06-13 Thread Klaus Wenninger
work on a 4-node and up cluster here. Regards, Klaus > > Best Regards, > Kazunori INOUE > >> -Original Message- >> From: Users [mailto:users-boun...@clusterlabs.org] On Behalf Of Klaus >> Wenninger >> Sent: Friday, May 25, 2018 4:08 PM >> To: users@cl

Re: [ClusterLabs] Questions about SBD behavior

2018-06-13 Thread 井上 和徳
Klaus > Wenninger > Sent: Friday, May 25, 2018 4:08 PM > To: users@clusterlabs.org > Subject: Re: [ClusterLabs] Questions about SBD behavior > > On 05/25/2018 07:31 AM, 井上 和徳 wrote: > > Hi, > > > > I am checking the watchdog function of SBD (without shared block-

Re: [ClusterLabs] Questions about SBD behavior

2018-05-28 Thread Andrei Borzenkov
On Mon, May 28, 2018 at 10:47 AM, Klaus Wenninger wrote: > On 05/28/2018 09:43 AM, Klaus Wenninger wrote: >> On 05/26/2018 07:23 AM, Andrei Borzenkov wrote: >>> 25.05.2018 14:44, Klaus Wenninger пишет: On 05/25/2018 12:44 PM, Andrei Borzenkov wrote: > On Fri, May 25,

Re: [ClusterLabs] Questions about SBD behavior

2018-05-28 Thread Klaus Wenninger
On 05/28/2018 09:43 AM, Klaus Wenninger wrote: > On 05/26/2018 07:23 AM, Andrei Borzenkov wrote: >> 25.05.2018 14:44, Klaus Wenninger пишет: >>> On 05/25/2018 12:44 PM, Andrei Borzenkov wrote: On Fri, May 25, 2018 at 10:08 AM, Klaus Wenninger wrote: > On

Re: [ClusterLabs] Questions about SBD behavior

2018-05-28 Thread Klaus Wenninger
On 05/26/2018 07:23 AM, Andrei Borzenkov wrote: > 25.05.2018 14:44, Klaus Wenninger пишет: >> On 05/25/2018 12:44 PM, Andrei Borzenkov wrote: >>> On Fri, May 25, 2018 at 10:08 AM, Klaus Wenninger >>> wrote: On 05/25/2018 07:31 AM, 井上 和徳 wrote: > Hi, > > I am

Re: [ClusterLabs] Questions about SBD behavior

2018-05-25 Thread Andrei Borzenkov
25.05.2018 14:44, Klaus Wenninger пишет: > On 05/25/2018 12:44 PM, Andrei Borzenkov wrote: >> On Fri, May 25, 2018 at 10:08 AM, Klaus Wenninger >> wrote: >>> On 05/25/2018 07:31 AM, 井上 和徳 wrote: Hi, I am checking the watchdog function of SBD (without shared

Re: [ClusterLabs] Questions about SBD behavior

2018-05-25 Thread Klaus Wenninger
On 05/25/2018 12:44 PM, Andrei Borzenkov wrote: > On Fri, May 25, 2018 at 10:08 AM, Klaus Wenninger wrote: >> On 05/25/2018 07:31 AM, 井上 和徳 wrote: >>> Hi, >>> >>> I am checking the watchdog function of SBD (without shared block-device). >>> In a two-node cluster, if one

Re: [ClusterLabs] Questions about SBD behavior

2018-05-25 Thread Andrei Borzenkov
On Fri, May 25, 2018 at 10:08 AM, Klaus Wenninger wrote: > On 05/25/2018 07:31 AM, 井上 和徳 wrote: >> Hi, >> >> I am checking the watchdog function of SBD (without shared block-device). >> In a two-node cluster, if one cluster is stopped, watchdog is triggered on >> the

Re: [ClusterLabs] Questions about SBD behavior

2018-05-25 Thread Klaus Wenninger
On 05/25/2018 07:31 AM, 井上 和徳 wrote: > Hi, > > I am checking the watchdog function of SBD (without shared block-device). > In a two-node cluster, if one cluster is stopped, watchdog is triggered on > the remaining node. > Is this the designed behavior? SBD without a shared block-device doesn't

[ClusterLabs] Questions about SBD behavior

2018-05-24 Thread 井上 和徳
Hi, I am checking the watchdog function of SBD (without shared block-device). In a two-node cluster, if one cluster is stopped, watchdog is triggered on the remaining node. Is this the designed behavior? [vmrh75b]# cat /etc/corosync/corosync.conf (snip) quorum { provider: