Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-dev@lists.linbit.com
Cc: Iustin Pop <iustin@google.com>
Subject: Re: [Drbd-dev] [PATCH 0/3] Implement {begin|after}-resync-source	handlers
Date: Tue, 18 May 2010 14:05:04 +0200	[thread overview]
Message-ID: <201005181405.04970.philipp.reisner@linbit.com> (raw)
In-Reply-To: <20100518085207.GB19087@google.com>

[..]
> > * Are you going to use them in your organisation?
> 
> That too, but better said we're going to use them in Ganeti (opensource,
> cluster-based virtualization manager). Background: Ganeti uses only the
> low-level drbdsetup interface, and not the drbdadm one, since we manage
> the minor numbers assignments dynamically. This dynamic part hits us,
> because we cannot make easy 'resync-after' rules (especially as on
> bigger Ganeti clusters, like 20-40 nodes, you could get easily into
> circular dependencies if you're not careful.
> 
> So the plan is to write a custom usermode_helper (right now Ganeti
> documentations says to use /bin/true :), so we're not losing any
> functionality by moving to a custom helper), that will simply restrict
> DRBD to a single sync (either incoming or outgoing) per machine, in
> order to not overload any machine's I/O resources. When a begin-sync
> request comes in, either source or target, the helper will look if any
> other minors are undergoing syncs, and if so will drbdsetup pause-sync
> the minor - I hope that this is safe to do from the callback, my few
> tests show it so. And when a after-resync-* requests comes, we look if
> there are any paused syncs (on our end), and if so then we'll unpause
> one.
> 
> Now, if drbd (the kernel driver) would have a setting like 'max_syncs',
> then we wouldn't have to implement anything in Ganeti, but that is
> probably more work in the kernel - which is harder, compared with a
> simple userspace shell script.
> 
> Hope my explanation makes sense…

Hi Iustin,

Yes, makes sense. It will go in, after the 8.3.8 release dust settled.

Best,
 Phil
-- 
: Dipl-Ing Philipp Reisner
: LINBIT | Your Way to High Availability
: Tel: +43-1-8178292-50, Fax: +43-1-8178292-82
: http://www.linbit.com

DRBD(R) and LINBIT(R) are registered trademarks of LINBIT, Austria.

      reply	other threads:[~2010-05-18 12:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-17 12:37 [Drbd-dev] [PATCH 0/3] Implement {begin|after}-resync-source handlers Iustin Pop
2010-05-17 12:37 ` [Drbd-dev] [PATCH 1/3] Implement before|after-resync-source in drbdadm Iustin Pop
2010-05-17 12:37 ` [Drbd-dev] [PATCH 2/3] Make the drbd driver generate resync-source callbacks Iustin Pop
2010-05-17 12:38 ` [Drbd-dev] [PATCH 3/3] Update documentation for resync-source handlers Iustin Pop
2010-05-17 21:44 ` [Drbd-dev] [PATCH 0/3] Implement {begin|after}-resync-source handlers Philipp Reisner
2010-05-18  8:52   ` Iustin Pop
2010-05-18 12:05     ` Philipp Reisner [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=201005181405.04970.philipp.reisner@linbit.com \
    --to=philipp.reisner@linbit.com \
    --cc=drbd-dev@lists.linbit.com \
    --cc=iustin@google.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox