Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 19631 invoked from network); 22 Feb 2008 09:45:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Feb 2008 09:45:10 -0000 Received: (qmail 927 invoked by uid 500); 22 Feb 2008 09:45:04 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 879 invoked by uid 500); 22 Feb 2008 09:45:04 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 869 invoked by uid 99); 22 Feb 2008 09:45:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Feb 2008 01:45:04 -0800 X-ASF-Spam-Status: No, hits=-1998.7 required=10.0 tests=ALL_TRUSTED,FS_REPLICA,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Feb 2008 09:44:17 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 905E9234C04F for ; Fri, 22 Feb 2008 01:44:19 -0800 (PST) Message-ID: <1884503632.1203673459589.JavaMail.jira@brutus> Date: Fri, 22 Feb 2008 01:44:19 -0800 (PST) From: "Henri van de Scheur (JIRA)" 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 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2872?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1257= 1330#action_12571330 ]=20 Henri van de Scheur commented on DERBY-2872: -------------------------------------------- Thanks a lot J=C3=B8rgen for your quick and descriptive replies! I regard all of my questions answered, apart from the last one, but that wa= s more due to a bad formulated question. I will try to explain it through a= n example. Especially the fact having '1 Master, 1 Slave', reduces a lot of possible f= ailure scenarios and makes it a lot easier. I just hadn't interpreted the s= pec this way.=20 Limited network communication to only 1 single socket, also limits possible= failure scenarios. So to question 9.=20 Let's say that Instance I1 is not able to send log for database D1 to the s= lave in Instance I2 at the required pace. I1 will then try to increase the = speed of log shipment. The latter might lead to reduced capacity in receivi= ng log from Instance I2 and database D2. This then might lead to increasing= speed of log shipment from instance I2, again leading to the same symptom:= reduced capacity of receiving log shipments from Instance I1, etc..... I hope this example makes my point more clear. But I guess response times w= ill increase avoiding this situation. > 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.