Return-Path: X-Original-To: apmail-db-derby-user-archive@www.apache.org Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C06F510268 for ; Mon, 22 Apr 2013 08:45:02 +0000 (UTC) Received: (qmail 15346 invoked by uid 500); 22 Apr 2013 08:45:02 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 14961 invoked by uid 500); 22 Apr 2013 08:45:02 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 14913 invoked by uid 99); 22 Apr 2013 08:45:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Apr 2013 08:45:00 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS,UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of knut.hatlen@oracle.com designates 141.146.126.69 as permitted sender) Received: from [141.146.126.69] (HELO aserp1040.oracle.com) (141.146.126.69) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Apr 2013 08:44:53 +0000 Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r3M8iVtE002541 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 22 Apr 2013 08:44:32 GMT Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r3M8iVJX012499 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 22 Apr 2013 08:44:31 GMT Received: from abhmt107.oracle.com (abhmt107.oracle.com [141.146.116.59]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r3M8iUDi000434 for ; Mon, 22 Apr 2013 08:44:30 GMT Received: from localhost (/10.172.139.141) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 22 Apr 2013 01:44:30 -0700 From: Knut Anders Hatlen To: "Derby Discussion" Subject: Re: Derby.properties not functioning for replication setting? References: <1366339352618-129455.post@n7.nabble.com> <1366342232892-129457.post@n7.nabble.com> Mail-Copies-To: never Mail-Followup-To: "Derby Discussion" Date: Mon, 22 Apr 2013 10:44:28 +0200 In-Reply-To: <1366342232892-129457.post@n7.nabble.com> (ping wei's message of "Thu, 18 Apr 2013 20:30:32 -0700 (PDT)") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Source-IP: acsinet21.oracle.com [141.146.126.237] X-Virus-Checked: Checked by ClamAV on apache.org ping wei writes: > Replication confirm is functioning as after failover replication ( properly > shutdown ), able to see table updated. > > However, if i waited a minute up to 10 minute, cut off the connection ( > shutdown slave derby service ) then connect again ( turn on slave derby > service ), i dont see any table udpate at all. ( if interval is working here > ) Hi, I think the max log shipping interval only makes sure the logs have been sent to the slave, and not that the slave has actually stored the logs to disk by that time. It sounds like you performed fail-over by shutting down the slave, and then the slave may lose transactions that it still hasn't stored to disk, even if it has the logs for those transactions in its buffers. Derby's replication service was designed to allow the slave to take over if the master goes down. In the experiment you described, it was the slave that went down rather than the master. The replication service doesn't ensure that the slave database is up to date with the master in this case. However, the master database should still have all the data. Hope this helps, -- Knut Anders