Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 79926 invoked from network); 24 Sep 2007 10:58:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 24 Sep 2007 10:58:14 -0000 Received: (qmail 32815 invoked by uid 500); 24 Sep 2007 10:58:04 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 32783 invoked by uid 500); 24 Sep 2007 10:58: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 32774 invoked by uid 99); 24 Sep 2007 10:58:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Sep 2007 03:58:04 -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; Mon, 24 Sep 2007 11:00:23 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id A859871420A for ; Mon, 24 Sep 2007 03:57:50 -0700 (PDT) Message-ID: <32674339.1190631470671.JavaMail.jira@brutus> Date: Mon, 24 Sep 2007 03:57:50 -0700 (PDT) From: "V.Narayanan (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-3064) Implement the LogShipper that will enable the shipping of Log records from the master to the slave In-Reply-To: <13994899.1189420769956.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529834 ] V.Narayanan commented on DERBY-3064: ------------------------------------ >If I understand you correctly, this time interval will only be helpful in the "too soon" case, not the >"too late" case. >When I wrote version 2 of the proof of concept patches (see DERBY-2872), I used a Daemon to >read log records at the slave side. I basically had: >performWork { > if (messageWaitingForProcess) processMessage(); >} >The waiting interval between each time performWork was called was way too high for this usage >(in the order of 3-10 seconds). This interval is probably too high for the log shipper as well, so >my guess is that you'll need something similar to an eternal loop with a wait(millis) somewhere in >this package. Does this mean atleast in the case of log shipper we would be forced to use threading since the DaemonService interval cannot be varied? Guess I have a LogShipper specific answer for DaemonService vs Threads if I am right. > Implement the LogShipper that will enable the shipping of Log records from the master to the slave > -------------------------------------------------------------------------------------------------- > > Key: DERBY-3064 > URL: https://issues.apache.org/jira/browse/DERBY-3064 > Project: Derby > Issue Type: Sub-task > Reporter: V.Narayanan > Assignee: V.Narayanan > Attachments: LogShipperImpl_v1.diff, LogShipperImpl_v1.stat > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.