Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Iustin Pop <iustin@google.com>
To: drbd-dev@lists.linbit.com
Subject: [Drbd-dev] Question regarding usermode_helper and lack of	{before|after}_resync_source
Date: Mon, 10 May 2010 17:30:12 +0200	[thread overview]
Message-ID: <20100510153012.GL5175@google.com> (raw)

Hi all,

I'm curious if there is a reason why there is before_resync_target but
not before_resync_source. Probably the rationale is that noone needed it
before :)

Background: the current capabilities to configure resync order or number
of resyncs per machine is doable either via manual pause-sync actions,
or via the syncer's '--after' parameter. However, in environment where
this is dynamic, it's hard to create a static map, and it would be
useful to have such a before_resync_source action that the helper can
act on - e.g. to pause the minor, to set its sync speed based on current
machine status, etc.

So… would it make sense to send a patch adding these two actions
(before/after)?

thanks,
iustin

                 reply	other threads:[~2010-05-10 15:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20100510153012.GL5175@google.com \
    --to=iustin@google.com \
    --cc=drbd-dev@lists.linbit.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