Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 31057 invoked from network); 4 Jul 2007 12:54:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Jul 2007 12:54:26 -0000 Received: (qmail 81829 invoked by uid 500); 4 Jul 2007 12:54:28 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 81795 invoked by uid 500); 4 Jul 2007 12:54:28 -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 81786 invoked by uid 99); 4 Jul 2007 12:54:28 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jul 2007 05:54:28 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jul 2007 05:54:25 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id BB067714224 for ; Wed, 4 Jul 2007 05:54:04 -0700 (PDT) Message-ID: <30747151.1183553644762.JavaMail.jira@brutus> Date: Wed, 4 Jul 2007 05:54:04 -0700 (PDT) From: =?utf-8?Q?J=C3=B8rgen_L=C3=B8land_=28JIRA=29?= 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#action_12510166 ]=20 J=C3=B8rgen L=C3=B8land commented on DERBY-2872: -------------------------------------- Link to the thread where Dag describes his proof-of-concept code: http://ww= w.mailinglistarchive.com/derby-dev@db.apache.org/msg25546.html A difference between the proof of concept codes: While Dag's code ships who= le log files, the poc attached to this issue ships individual log records. > Add Replication functionality to Derby > -------------------------------------- > > Key: DERBY-2872 > URL: https://issues.apache.org/jira/browse/DERBY-2872 > Project: Derby > Issue Type: New Feature > Components: Miscellaneous > Affects Versions: 10.4.0.0 > Reporter: J=C3=B8rgen L=C3=B8land > Attachments: proof_of_concept_master.diff, proof_of_concept_maste= r.stat, proof_of_concept_slave.diff, proof_of_concept_slave.stat, replicati= on_funcspec.html, replication_script.txt > > > 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.