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 DEC09F45F for ; Mon, 22 Apr 2013 10:24:00 +0000 (UTC) Received: (qmail 10166 invoked by uid 500); 22 Apr 2013 10:24:00 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 9940 invoked by uid 500); 22 Apr 2013 10:24:00 -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 9906 invoked by uid 99); 22 Apr 2013 10:23:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Apr 2013 10:23:59 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: error (nike.apache.org: encountered temporary error during SPF processing of domain of pingweitan@gmail.com) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Apr 2013 10:23:53 +0000 Received: from tom.nabble.com ([192.168.236.105]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1UUDTq-0007sm-0J for derby-user@db.apache.org; Mon, 22 Apr 2013 02:56:14 -0700 Date: Mon, 22 Apr 2013 02:56:13 -0700 (PDT) From: ping wei To: derby-user@db.apache.org Message-ID: <1366624573998-129558.post@n7.nabble.com> In-Reply-To: References: <1366339352618-129455.post@n7.nabble.com> <1366342232892-129457.post@n7.nabble.com> Subject: Re: Derby.properties not functioning for replication setting? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi Knut Anders, Replication is working fine. The intention of trying to make sure master has data sent to slave is to keep the network port open. Due to network security, port is set to close off in 30 minutes if no data is transported. Once the network port closed, replication down. As long as properly failover at master, slave should have all data in-sync ( am i right ? ), so this wouldn't be a problem. Also, understood that if emergency case happen, there might be possibility of losing small chunk of data. Does it mean the data actually sent over and stored in slave buffer? ( back to my intention of making sure there is data sent over to keep the replication port open ) Anyway to rectify that replication is replicating data over? I have set "derby.replication.verbose=true" but doesnt see replicating data logging down although i keep pumping data over, and after fail-over, i seen the data at slave updated. Anything i miss out or is there an alternative way for replication to keep alive? Appreciate your help, thanks a lot. Regards, Ping Wei. -- View this message in context: http://apache-database.10148.n7.nabble.com/Derby-properties-not-functioning-for-replication-setting-tp129455p129558.html Sent from the Apache Derby Users mailing list archive at Nabble.com.