[jira] Issue Comment Edited: (DERBY-2872) Add Replication functionality to Derby

["Jørgen Løland (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565747#action_12565747 ] 

jorgenlo edited comment on DERBY-2872 at 2/5/08 5:51 AM:
--------------------------------------------------------------

Hi Dibyendu,

The replication factories depend on functionality in 
* store (mainly store.raw.RawStore and store.raw.log.LogToFile and LogAccessFile) 
* the database modules (BasicDatabase and SlaveDatabase). 

The replication functionality in EmbedConnection is only related to processing connection attempts with replication commands ( {start|stop}{Master|Slave} and failover - see funcspec)

In retrospect, I think o.a.d.i.store.raw.replication or maybe o.a.d.i.store.replication would be a better place for the replication factories than services.  

Hope this helps

      was (Author: jorgenlo):
    Hi Dibyendu,

The replication factories depend on functionality in 
* store (mainly store.raw.RawStore and store.raw.log.LogToFile and LogAccessFile) 
* the database modules (BasicDatabase and SlaveDatabase). 

The replication functionality in EmbedConnection is only related to processing connection attempts with replication commands ( {start|stop}{Master|Slave} and failover - see funcspec)

In retrospect, I think o.a.d.i.store.raw.replication or maybe o.a.d.i.store.replication would be a better place for the replication factories that services.  

Hope this helps
  
> 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ø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_script.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 these:
> 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.