[ https://issues.apache.org/jira/browse/DERBY-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555645#action_12555645 ]
Kim Haase commented on DERBY-2872: ---------------------------------- Sorry, something else in the spec is not quite clear to me. Is it correct that to start replication, all you need to do is specify the startMaster/slavehost/[slaveport] attributes on the master database? It appears from the description that this command gets things going on both the master and the slave without your having to explicitly run startSlave on the slave system. It appears that something like this happens when you stop the master, so I'm assuming it happens when you start it too. If that is the case, what is the startSlave attribute used for? Is it only used if the slave-to-master connection is lost? But in that case, according to the Failure Scenarios section, the slave automatically tries to reestablish the connection, unless I've misunderstood. Thanks for any clarifications. > 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/[EMAIL > PROTECTED] > 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.