Hello,
After experiencing several dual-node failures due to faulty RAID
controller on one of nodes (it is famous 3ware 9650-16ML, which may
reset and do not respond for 30 seconds at all due to command sent to
its control channel) I noticed 'disk-timeout' option which may help with
such issue.
guys .. I'm in big trouble here ...
My heartbeat is changing from one server to another in loop.
The following configuration files
root@servidor-01:~# cat /etc/drbd.conf
global {
usage-count no;
}
resource r0 {
protocol C;
startup {
wfc-timeout 30;
We have a pretty standard setup
MASTER --- SLAVE (STANDBY)
both nodes are in sync without much issue now but during this week our DC
will perform some maintenance tasks that might incur in some connectivity
issues between both nodes.
How can put the slave node in maintenance (or any other mode)
Wow! Those are some old versions!
Just “drbdadm disconnect all” on the Primary node before the maintenance and
“drbdadm connect all” afterwards. All else is magic!
Dan
From: drbd-user-boun...@lists.linbit.com
[mailto:drbd-user-boun...@lists.linbit.com] On Behalf Of Gabriel Sosa
Sent: Tuesday,
So the slave will catch up afterwards. Excellent.
Thanks
On Tue, Sep 24, 2013 at 5:19 PM, Dan Barker dbar...@visioncomm.net wrote:
Wow! Those are some old versions!
** **
Just “drbdadm disconnect all” on the Primary node before the maintenance
and “drbdadm connect all” afterwards.
Hi all,
I have a 2 node set up with both nodes in my server room using a GB
Ethernet direct connection between NICs for the DRBD resources using
Protocol C and single primary. It's working nicely.
We want now to add a third node using probably Protocol A at an off site
location to be used
