Return-Path: Delivered-To: apmail-hadoop-hbase-issues-archive@minotaur.apache.org Received: (qmail 9204 invoked from network); 23 Mar 2010 06:26:49 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 23 Mar 2010 06:26:49 -0000 Received: (qmail 55482 invoked by uid 500); 23 Mar 2010 06:26:48 -0000 Delivered-To: apmail-hadoop-hbase-issues-archive@hadoop.apache.org Received: (qmail 55453 invoked by uid 500); 23 Mar 2010 06:26:48 -0000 Mailing-List: contact hbase-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-issues@hadoop.apache.org Delivered-To: mailing list hbase-issues@hadoop.apache.org Received: (qmail 55445 invoked by uid 99); 23 Mar 2010 06:26:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Mar 2010 06:26:48 +0000 X-ASF-Spam-Status: No, hits=-1103.5 required=10.0 tests=ALL_TRUSTED,AWL 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; Tue, 23 Mar 2010 06:26:47 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 67808234C495 for ; Tue, 23 Mar 2010 06:26:27 +0000 (UTC) Message-ID: <902346253.426981269325587423.JavaMail.jira@brutus.apache.org> Date: Tue, 23 Mar 2010 06:26:27 +0000 (UTC) From: "stack (JIRA)" To: hbase-issues@hadoop.apache.org Subject: [jira] Updated: (HBASE-2340) Add end-to-end test of sync/flush MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-2340: ------------------------- Attachment: 2244-v6.patch TestFullLogReconstruction works now after enabling dfs.append.support=true (and other configs. from Nicolas hbase-2345) and making it so exiting regionserver doesn't shutdown the filesystem (because then the filesystem is closed for daemons in the JVM). The test runs for 200 seconds, mostly because we're loading up a good bit of data. Could make it less I suppose. I see this in test log: {code} 2010-03-22 23:10:33,232 INFO [HMaster] regionserver.HLog(1096): Splitting 1 hlog(s) in hdfs://localhost:61468/user/stack/.logs/192.168.1.157,61497,1269324534078 2010-03-22 23:10:33,232 DEBUG [HMaster] regionserver.HLog(1183): Splitting hlog 1 of 1: hdfs://localhost:61468/user/stack/.logs/192.168.1.157,61497,1269324534078/hlog.dat.1269324534191, length=0 2010-03-22 23:10:33,233 WARN [IPC Server handler 8 on 61468] namenode.FSNamesystem(1144): DIR* NameSystem.startFile: failed to create file /user/stack/.logs/192.168.1.157,61497,1269324534078/hlog.dat.1269324534191 for DFSClient_343812212 on client 127.0.0.1 because current leaseholder is trying to recreate file. 2010-03-22 23:10:33,240 INFO [HMaster] regionserver.HLog(1427): Failed open for append, waiting on lease recovery: hdfs://localhost:61468/user/stack/.logs/192.168.1.157,61497,1269324534078/hlog.dat.1269324534191 org.apache.hadoop.ipc.RemoteException: org.apache.hadoop.hdfs.protocol.AlreadyBeingCreatedException: failed to create file /user/stack/.logs/192.168.1.157,61497,1269324534078/hlog.dat.1269324534191 for DFSClient_343812212 on client 127.0.0.1 because current leaseholder is trying to recreate file. ... {code} ... and after RS fully goes down we're able to open the log and process its content. > Add end-to-end test of sync/flush > --------------------------------- > > Key: HBASE-2340 > URL: https://issues.apache.org/jira/browse/HBASE-2340 > Project: Hadoop HBase > Issue Type: Task > Reporter: stack > Assignee: stack > Priority: Blocker > Fix For: 0.20.4, 0.21.0 > > Attachments: 2244-v6.patch, 2340.patch > > > Add a test to do the following: > {code} > + Start a HBase/HDFS cluster (local node is fine). > + Use top-level (HTable) level APIs to put items. > + Try about single column puts, as well as puts which span multiple columns/multiple column families, etc. > + Then kill one region server. > + Wait for recovery to happen. > + And then check the rows exist. > {code} > Assigning myself. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.