<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.28.2">
</HEAD>
<BODY>
>We had a similar situation, <BR>
><BR>
By the way how much wan link do you have then ?<BR>
<BR>
>though it was with CentOS and Apache/MySQL, not Orrible.<BR>
><BR>
Horrible ... Orrible .. Oracle ;-)<BR>
<BR>
>Write performance was better with protocol A than it was with C.<BR>
><BR>
Thanks for sharing/feedback<BR>
<BR>
>but even with protocol A, there's been no data loss yet.<BR>
><BR>
great to know this, once again thanks for sharing.<BR>
<BR>
would you also share when using Protocol A, whats the size of <BR>
'sendbuf-size' your are/were using ? because I think sendbuf-size <BR>
should be high(exactly how much I don't know) when using Protocol A. <BR>
And exactly how much bandwidth do you have in b/w the two nodes ?<BR>
<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
--<BR>
Regards,<BR>
Muhammad Sharfuddin | NDS Technologies Pvt Ltd | cell: +92-333-2144823 | UAN: +92-21-111-111-142 ext: 113<BR>
<BR>
Micro$oft had developed .NET trading platform for the London Stock Exchange(LSE), claiming that it provided "five nines" reliability.<BR>
After suffering extended downtime and unreliability the LSE announced in 2009 that it was planning to drop its <BR>
Micro$oft solution and switch to a Linux based one in 2010<FONT SIZE="2">.</FONT><BR>
<BR>
Your Linux is Ready<BR>
<A HREF="http://www.novell.com/linux/">http://www.novell.com/linux</A> <BR>
<BR>
</TD>
</TR>
</TABLE>
On Mon, 2011-01-31 at 08:09 -0700, Matt Graham wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
From: Muhammad Sharfuddin <<A HREF="mailto:M.Sharfuddin@nds.com.pk">M.Sharfuddin@nds.com.pk</A>>
> OS: SLES11 SP1 x86
> SLE HAE 11 SP1
> DRBD version: 8.3.7
> /dev/drbd0 is an oracle file system(/opt/oracle)
> We are having serious performance issues when using DRBD over a very
> slow but a very reliable WAN link(2.5 Mbps). As of now we are using
> Protocol C, and now we are [thinking about using] Protocol A.
> Anyone please suggest/recommend/comments
We had a similar situation, though it was with CentOS and Apache/MySQL, not
Orrible. Write performance was better with protocol A than it was with C.
Switching protocols was easy, though we weren't working with live data when we
did the switch. There have been two unplanned flailovers in the last 8
months, but even with protocol A, there's been no data loss yet.
Note that YMMV on this, but it's worked for us. Caveat user.
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>