Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] The drbd resync process
Date: Fri, 8 Aug 2008 11:15:53 +0200	[thread overview]
Message-ID: <20080808091553.GB9742@soda.linbit> (raw)
In-Reply-To: <1218183403.3749.16.camel@niko.infocore.cn>

On Fri, Aug 08, 2008 at 04:16:43PM +0800, niko wrote:
> Consider node A crashed as primary and rejoining the cluster,B as the
> surviving node.
> What's the resync process ?
> 
> I can't find how the drbd_start_resync () function call the
> w_make_resync_request() to send RSDataRequest message to the SyncSource

it is "queued for the worker",
and requeued via a timer.

> When the peer node recovers or the connection is re-established, DRBD
> combines the bitmap information from both nodes to determine the total
> data set that it must re-synchronize.
> 
> Why DRBD needs to combines the bitmap information from both nodes since
> one is Primary,the other is Secondary?

both nodes may have changed the data independently.

> Thanks ,I'm just a learner.

now, I'd like to learn a bit more about you, still. so let me repeat my
question,

What is your motivation for this?
How can you help us?
How can you help us help you?


-- 
: Lars Ellenberg                            Tel +43-1-8178292-55 :
: LINBIT Information Technologies GmbH      Fax +43-1-8178292-82 :
: Vivenotgasse 48, A-1120 Vienna/Europe    http://www.linbit.com :

      reply	other threads:[~2008-08-08  9:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080806100003.E28A12E3A53E@mail.linbit.com>
2008-08-08  8:16 ` [Drbd-dev] The drbd resync process niko
2008-08-08  9:15   ` Lars Ellenberg [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=20080808091553.GB9742@soda.linbit \
    --to=lars.ellenberg@linbit.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