Robert.Koeppl at knapp
Feb 16, 2012, 11:33 PM
Post #1 of 1
You may wish to have a look at the timeout values in the DRBD.conf. They
Antwort: Re: replication link stability
probably are on the low side for your network thus causing DRBD think you
have connection outages where in fact it just has latency.
ping-timeout, connect-int, timeout
are the the variables to look at. Default Values are optimised for wired
Mit freundlichen Grüßen / Best Regards
Customer Support & Projects
Teamleader IT Support
KNAPP Systemintegration GmbH
8700 Leoben, Austria
Phone: +43 3842 805-322
Fax: +43 3842 82930-500
robert.koeppl [at] knapp
Commercial register number: FN 138870x
Commercial register court: Leoben
The information in this e-mail (including any attachment) is confidential
and intended to be for the use of the addressee(s) only. If you have
received the e-mail by mistake, any disclosure, copy, distribution or use
of the contents of the e-mail is prohibited, and you must delete the
e-mail from your system. As e-mail can be changed electronically KNAPP
assumes no responsibility for any alteration to this e-mail or its
attachments. KNAPP has taken every reasonable precaution to ensure that
any attachment to this e-mail has been swept for virus. However, KNAPP
does not accept any liability for damage sustained as a result of such
attachment being virus infected and strongly recommend that you carry out
your own virus check before opening any attachment.
Piotr Kandziora <raveenpl [at] gmail>
Gesendet von: drbd-user-bounces [at] lists
Digimer <linux [at] alteeve>
drbd-user [at] lists
Re: [DRBD-user] replication link stability
Thanks for your answer. DRBD Proxy could be a solution, but it is not
possible for today.
I am thinking of trying DRBD with protocol A, but currently I am not able
to test on my environment as it is in production. I will have maintenance
window on the weekend. Do you think it can help? If yes, may you suggest
values for tcp send buffer?
Thanks in advance.
On Thu, Feb 16, 2012 at 4:43 PM, Digimer <linux [at] alteeve> wrote:
Samba (and similar protocols) are generally pretty forgiving of
network issues, so it's not a surprise that they work where DRBD does
not. DRBD is designed for high speed/low latency environments, and has a
fair bit of attention paid to fault detection and recovery. If it sees a
network fault, even a short one, it has to assume the link has failed
and recovery is needed. This does not lend itself well to use on
slow/error prone networks.
Is it possible to use a wired connection for the DRBD replication? If
not, I would suggest looking at DRBD Proxy instead, as it is designed to
run over slow/unstable links, but it is asynchronous, so be advised that
consistency is not always guaranteed.
drbd-user mailing list
drbd-user [at] lists