From: Stan Hoeppner <stan@hardwarefreak.com>
To: Ethan Wilson <ethan.wilson@shiftmail.org>,
linux-raid <linux-raid@vger.kernel.org>
Subject: Re: md with shared disks
Date: Thu, 13 Nov 2014 18:07:53 -0600 [thread overview]
Message-ID: <546547D9.3030701@hardwarefreak.com> (raw)
In-Reply-To: <54653661.80605@shiftmail.org>
On 11/13/2014 04:53 PM, Ethan Wilson wrote:
> On 13/11/2014 21:56, Stan Hoeppner wrote:
>> With DRBD and GFS2 it is true active/active at the block level. You
>> just lose half your disk capacity due to the host-to-host mirroring.
>
> Sorry but I don't share your definition of active/active.
>
> Would you say that a raid1 is an active/active thing?
>
> Doubling the number of disks and repeating the operation on both sides
> is not active/active in the sense that people usually want.
>
> Active/active commonly means that you have twice the performance of
> active/passive.
>
> In this sense DRBD not only is an active/passive but it is even way
> below the performances of an active/passive because it has to transmit
> the data to the peer in addition to write to the disks, and this takes
> CPU time for memcpy and interrupts, introduces latency, requires
> additional hardware (= fast networking dedicated to DRBD). An
> active/passive with shared disks is hence "twice" (very roughly) faster
> than DRBD at the same price spent on the head nodes. An active/active
> with shared disks is hence 4 times (again very roughly) faster than
> DRBD, at the same price for the head nodes.
>
> In addition to this with DRBD you have to buy twice the number of disks,
> which is also an additional expense. Marginally though, because a
> shared-disk infrastructure is way more expensive than a direct-attached
> one, but it has to be planned like that in advance, and not retrofitted
> like you propose.
>
> His current infrastructure cannot be easily converted to DRBD without
> major losses: if he attempts to do so he will have almost double the
> costs of a basic DRBD shared-nothing direct-attached infrastructure or
> exactly double the cost of a shared-disk infrastructure, intended as
> cost per TB of data. Unfortunately, after this he will still have half
> the performances of an active/passive shared-disk clustered-MD solution.
He doesn't have an infrastructure yet. He's attempting to build one but
purchased the wrong gear for his requirements. I presented him with
options to do it the right way, and to salvage what he has already
purchased. The DRBD active/active option is the latter. The SAN option
was the former. You seem to have misunderstood my comments.
Cheers,
Stan
prev parent reply other threads:[~2014-11-14 0:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-09 8:30 md with shared disks Anton Ekermans
2014-11-10 16:40 ` Ethan Wilson
2014-11-10 22:14 ` Stan Hoeppner
2014-11-13 13:14 ` Anton Ekermans
2014-11-13 20:56 ` Stan Hoeppner
2014-11-13 22:53 ` Ethan Wilson
2014-11-14 0:07 ` Stan Hoeppner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=546547D9.3030701@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=ethan.wilson@shiftmail.org \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.