[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [dm-devel] [PATCH v3 0/4] dm-replicator: introduce new remote replication target

On 2009-12-01T17:05:03, heinzm redhat com wrote:

> * 3rd version of patch series (dated Oct 23 2009) *
> Reworked to allow for Build after each single patch has been applied.

Hi Heinz, have you considered a git tree? Might make it easier to review

> This is a series of 4 patches introducing the device-mapper remote
> data replication target "dm-replicator" to kernel 2.6.
> Userspace support for remote data replication will be in
> a future LVM2 version.

Is there any code available for testing this yet?

> The target supports disaster recovery by replicating groups of active
> mapped devices (ie. receiving io from applications) to one or more
> remote sites to paired groups of equally sized passive block devices
> (ie. no application access). Synchronous, asynchronous replication
> (with fallbehind settings) and temporary downtime of transports
> are supported.

How is resync handled - peer-to-peer or relayed via the master? 

What about device failures / IO errors at the sites?

> It utilizes a replication log to ensure write ordering fidelity for
> the whole group of replicated devices, hence allowing for consistent
> recovery after failover of arbitrary applications
> (eg. DBMS utilizing N > 1 devices).

Write ordering is not guaranteed across different file systems / block
devices today; so no DBMS actually requires this. What is the benefit?

What kind of reordering on a per-device basis is allowed via this
infrastructure at each site? (drbd has logic to detect implicit write
dependencies to allow peers to optimize local IO.)

> A "blockdev" site link module implements block devices access to all remote
> devices, ie. all devices exposed via the Linux block device layer
> (eg. iSCSI, FC).

> Again, other eg. network type transport site link handlers may
> follow as plugins.

How is all of this actually configured and used?

> Please review for upstream inclusion.

Should this not be Cc'ed to LKML if you aim for upstream inclusion? I
actually would expect that most of the criticism of drbd's inclusion
would also apply here, no? (With the added point that dm-replicator does
not actually have any users yet.)


Architect Storage/HA, OPS Engineering, Novell, Inc.
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG N├╝rnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]