Re: [ClusterLabs] Merging partitioned two_node cluster?

2020-05-05 Thread Nickle, Richard
. Technical Services Engineer* Information Technology Services rnic...@holycross.edu *phone: *(508) 793-2569 www.holycross.edu On Tue, May 5, 2020 at 12:49 PM Andrei Borzenkov wrote: > 05.05.2020 19:30, Nickle, Richard пишет: > > So I tried an experiment. I had tried switch over to 'udpu

Re: [ClusterLabs] Merging partitioned two_node cluster?

2020-05-05 Thread Nickle, Richard
of my base network in 'bindnetaddr' doesn't account for networks with CIDR mask bits greater than 24? (which would have non-zero least significant bytes.) Thanks, Rick On Tue, May 5, 2020 at 12:03 PM Andrei Borzenkov wrote: > 05.05.2020 16:44, Nickle, Richard пишет: > > Tha

Re: [ClusterLabs] Merging partitioned two_node cluster?

2020-05-05 Thread Nickle, Richard
128 KBytes 1.05 Mbits/sec [ 3] 0.0- 3.0 sec 386 KBytes 1.05 Mbits/sec [ 3] Sent 269 datagrams Thanks, Rick On Tue, May 5, 2020 at 1:54 AM Andrei Borzenkov wrote: > 05.05.2020 06:39, Nickle, Richard пишет: > > I have a two node cluster managing a VIP. The service is an SMTP

[ClusterLabs] Merging partitioned two_node cluster?

2020-05-04 Thread Nickle, Richard
I have a two node cluster managing a VIP. The service is an SMTP service. This could be active/active, it doesn't matter which node accepts the SMTP connection, but I wanted to make sure that a VIP was in place so that there was a well-known address. This service has been running for quite

Re: [ClusterLabs] DRBD / LVM Global Filter Question

2020-04-03 Thread Nickle, Richard
On Fri, Apr 3, 2020 at 7:43 AM Eric Robinson wrote: > Greetings, > > > >1. If DRBD lives **below** or **between** LVM volumes, then: > > > >1. set global_filter to reject the DRBD backing devices > 2. set write_cache_state = 0 > 3. set use_lvmetad = 0 > 4. set

Re: [ClusterLabs] DRBD not failing over

2020-02-26 Thread Nickle, Richard
I spent many, many hours tackling the two-node problem and I had exactly the same symptoms (only able to get the resource to move if I moved it manually) until I did the following: * Switch to DRBD 9 (added LINBIT repo because DRBD 8 is the default in the Ubuntu repo) * Build a third diskless

Re: [ClusterLabs] 2-node DRBD Pacemaker not performing as expected: Where to next?

2019-08-20 Thread Nickle, Richard
Thu, 2019-08-15 at 11:25 -0400, Nickle, Richard wrote: > > > > My objective is two-node active/passive DRBD device which would > > automatically fail over, a secondary objective would be to use > > standard, stock and supported software distributions and repositories >

[ClusterLabs] 2-node DRBD Pacemaker not performing as expected: Where to next?

2019-08-15 Thread Nickle, Richard
My objective is two-node active/passive DRBD device which would automatically fail over, a secondary objective would be to use standard, stock and supported software distributions and repositories with as little customization as possible. I'm using Ubuntu 18.04.3, plus the DRBD, corosync and

[ClusterLabs] Ubuntu 18.04 and corosync-qdevice

2019-08-09 Thread Nickle, Richard
I've built a two-node DRBD cluster with SBD and STONITH, following advice from ClusterLabs, LinBit, Beekhof's blog on SBD. I still cannot get automated failover when I down one of the nodes. I thought that perhaps I needed to have an odd-numbered quorum so I attempted to follow the