Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1674297345.1203669259643.JavaMail.jira@brutus>
Date: Fri, 22 Feb 2008 00:34:19 -0800 (PST)
From: =?utf-8?Q?J=C3=B8rgen_L=C3=B8land_=28JIRA=29?= <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-2872) Add Replication functionality to
 Derby
In-Reply-To: <16039538.1182851726399.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/DERBY-2872?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1257=
1307#action_12571307 ]=20

J=C3=B8rgen L=C3=B8land commented on DERBY-2872:
--------------------------------------

Retrying example in answer to Q3 - (probably not looking good, but at least=
 readable):

Derby Inst 1.....Derby Inst 2.....Derby Inst 3
Normal: 'db1'
Master: 'db2'...Slave: 'db2'
Master: 'db3'..............................Slave: 'db3'
Slave: 'db4'.....Master: 'db4'
....................................................Normal: 'db5'=20

> Add Replication functionality to Derby
> --------------------------------------
>
>                 Key: DERBY-2872
>                 URL: https://issues.apache.org/jira/browse/DERBY-2872
>             Project: Derby
>          Issue Type: New Feature
>          Components: Replication
>    Affects Versions: 10.4.0.0
>            Reporter: J=C3=B8rgen L=C3=B8land
>            Assignee: J=C3=B8rgen L=C3=B8land
>         Attachments: master_classes_1.pdf, poc_master_v2.diff, poc_master=
_v2.stat, poc_master_v2b.diff, poc_slave_v2.diff, poc_slave_v2.stat, poc_sl=
ave_v2b.diff, poc_slave_v2c.diff, proof-of-concept_v2b-howto.txt, proof_of_=
concept_master.diff, proof_of_concept_master.stat, proof_of_concept_slave.d=
iff, proof_of_concept_slave.stat, replication_funcspec.html, replication_fu=
ncspec_v2.html, replication_funcspec_v3.html, replication_funcspec_v4.html,=
 replication_funcspec_v5.html, replication_funcspec_v6.html, replication_fu=
ncspec_v7.html, replication_funcspec_v8.html, replication_funcspec_v9.html,=
 replication_script.txt, slave_classes_1.pdf
>
>
> It would be nice to have replication functionality to Derby; many potenti=
al Derby users seem to want this. The attached functional specification lis=
ts some initial thoughts for how this feature may work.
> Dag Wanvik had a look at this functionality some months ago. He wrote a p=
roof of concept patch that enables replication by copying (using file syste=
m copy) and redoing the existing Derby transaction log to the slave (unfort=
unately, I can not find the mail thread now).
> DERBY-2852 contains a patch that enables replication by sending dedicated=
 logical log records to the slave through a network connection and redoing =
these.
> Replication has been requested and discussed previously in multiple threa=
ds, including these:
> http://mail-archives.apache.org/mod_mbox/db-derby-user/200504.mbox/%3c426=
E04C1.1070904@yahoo.de%3e
> http://www.nabble.com/Does-Derby-support-Transaction-Logging---t2626667.h=
tml

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.