db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2872) Add Replication functionality to Derby
Date Sun, 02 Mar 2008 17:26:51 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

V.Narayanan updated DERBY-2872:

    Attachment: ReplicationDesign.pdf

I started working on a replication wiki over the weekend. I spent the weekend writing down
initial set of details that I thought the wiki should contain and which would be relevant
to a
new user of the replication feature. I wrote these details in the form of a text file. 

I would be converting the text file into a replication wiki over the next week. 

Since this issue deals with the replication design and tries to identify issues that are relevant

to this feature I am attaching whatever information I have assimilated to this issue.

Note that the attached pdf contains a very simplified block diagram of the main modules involved
in replication. I purposely made this simplified to enable the easy understanding of the replication

More detailed descriptions of the feature can be got by following the JIRA pointers that are
in the explanations of the various blocks of this simplified block diagram, and going through
specific JIRA issues.

I have tried to organize the information I have collected or re-collected so that it will
be easy
for reviewers to point out places in which I have gone wrong.

I will be making further updates, improvements and modifications directly to the wiki and
will not
be attaching it to this issue.

> 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:
>            Reporter: Jørgen Løland
>            Assignee: Jørgen Løland
>         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_slave_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.diff, proof_of_concept_slave.stat,
replication_funcspec.html, replication_funcspec_v2.html, replication_funcspec_v3.html, replication_funcspec_v4.html,
replication_funcspec_v5.html, replication_funcspec_v6.html, replication_funcspec_v7.html,
replication_funcspec_v8.html, replication_funcspec_v9.html, replication_script.txt, ReplicationDesign.pdf,
ReplicationWriteup.txt, slave_classes_1.pdf
> It would be nice to have replication functionality to Derby; many potential Derby users
seem to want this. The attached functional specification lists some initial thoughts for how
this feature may work.
> Dag Wanvik had a look at this functionality some months ago. He wrote a proof of concept
patch that enables replication by copying (using file system copy) and redoing the existing
Derby transaction log to the slave (unfortunately, 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 threads, including
> http://mail-archives.apache.org/mod_mbox/db-derby-user/200504.mbox/%3c426E04C1.1070904@yahoo.de%3e
> http://www.nabble.com/Does-Derby-support-Transaction-Logging---t2626667.html

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

View raw message