Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
>We had a similar situation, > By the way how much wan link do you have then ? >though it was with CentOS and Apache/MySQL, not Orrible. > Horrible ... Orrible .. Oracle ;-) >Write performance was better with protocol A than it was with C. > Thanks for sharing/feedback >but even with protocol A, there's been no data loss yet. > great to know this, once again thanks for sharing. would you also share when using Protocol A, whats the size of 'sendbuf-size' your are/were using ? because I think sendbuf-size should be high(exactly how much I don't know) when using Protocol A. And exactly how much bandwidth do you have in b/w the two nodes ? -- Regards, Muhammad Sharfuddin | NDS Technologies Pvt Ltd | cell: +92-333-2144823 | UAN: +92-21-111-111-142 ext: 113 Micro$oft had developed .NET trading platform for the London Stock Exchange(LSE), claiming that it provided "five nines" reliability. After suffering extended downtime and unreliability the LSE announced in 2009 that it was planning to drop its Micro$oft solution and switch to a Linux based one in 2010. Your Linux is Ready http://www.novell.com/linux On Mon, 2011-01-31 at 08:09 -0700, Matt Graham wrote: > From: Muhammad Sharfuddin <M.Sharfuddin at nds.com.pk> > > 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20110131/982b8796/attachment.htm>