Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-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 4624D4EDF for ; Thu, 23 Jun 2011 17:04:28 +0000 (UTC) Received: (qmail 36001 invoked by uid 500); 23 Jun 2011 17:04:26 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 35970 invoked by uid 500); 23 Jun 2011 17:04:26 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 35959 invoked by uid 99); 23 Jun 2011 17:04:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Jun 2011 17:04:26 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jdcryans@gmail.com designates 74.125.83.41 as permitted sender) Received: from [74.125.83.41] (HELO mail-gw0-f41.google.com) (74.125.83.41) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Jun 2011 17:04:18 +0000 Received: by gwaa12 with SMTP id a12so1023837gwa.14 for ; Thu, 23 Jun 2011 10:03:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=+95LWmrzrGZNAwrhwu2FznN5AfUXNWkFkd3hkZ1yIb4=; b=R+fdRHKubU7ivZIkRC87Y5UwSlDEFEwx0Le/YXaGRy6v8cZR1+YaRV2T/AeMfQ79oL mMaJqld9W/QeAxwpl0y5A6oRx8XEXa3HpEahcKBPmdm2dj+sjknPYzmWUOsiJ68tVig1 TtVYbeskjbuwd8ACIM3o/Xd+kLCrtoswcNV6c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=IT0e3W94i21nKlBMnDlpXf3QtlZiaXGv320zFwDzKpKjvi83i2z5vVBZpnaMcdWx4z sE9o7fdmireqbHcq7buJjOdBS7Zc+M4ImBWpXAROLBiGtk5OFS8NtY1PZvACpqIvnsSp zua/52D4FJ/cGOPupmpV/+J3jF5/HOB2wRZyU= MIME-Version: 1.0 Received: by 10.101.179.39 with SMTP id g39mr2424408anp.96.1308848637686; Thu, 23 Jun 2011 10:03:57 -0700 (PDT) Sender: jdcryans@gmail.com Received: by 10.100.226.14 with HTTP; Thu, 23 Jun 2011 10:03:57 -0700 (PDT) In-Reply-To: References: Date: Thu, 23 Jun 2011 10:03:57 -0700 X-Google-Sender-Auth: uHpLwtN2CaOMkR-6A7fIYqI9BKw Message-ID: Subject: Re: checkAndPut() failing with NotServingRegionException From: Jean-Daniel Cryans To: user@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Getting RetriesExhaustedWithDetailsException due to NSRE means that it took forever for a region server to close or split a region, what you pasted from the region server talks a region closing but that also happens during split. I'd suggest digging more in those region server logs using this guide: http://hbase.apache.org/book/trouble.html Also make sure you review this http://hbase.apache.org/book/performance.htm= l Finally giving a 1GB heap to HBase while inserting a lot of data is like making a malnourished child work in a coal mine, it's not very nice of you. J-D On Wed, Jun 22, 2011 at 11:06 PM, Sam Seigal wrote: > Hi, > > I am loading data into my HBase cluster and running into two issues - > > During my import, I received the following exception -> > > org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Fail= ed > 53484 actions: servers with issues: spock7001:60020, > =A0 =A0 =A0 =A0at > org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementati= on.processBatch(HConnectionManager.java:1220) > =A0 =A0 =A0 =A0at > org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementati= on.processBatchOfPuts(HConnectionManager.java:1234) > =A0 =A0 =A0 =A0at > org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:819) > =A0 =A0 =A0 =A0at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java= :675) > =A0 =A0 =A0 =A0at org.apache.hadoop.hbase.client.HTable.put(HTable.java:6= 60) > > May have cluster issues =3D> true > Cause 0 > > When I check the logs on the regions server, the last thrown exception is > the following =3D> > > Thu Jun 23 05:16:18 2011 GMT regionserver 10460-0@spock7001:0 [DEBUG] (IP= C > Server handler 7 on 60020) > { org.apache.hadoop.hbase.NotServingRegionException: > hbaseTable,,1308805558566.5aefc6c2b9599f55f8b40351a61db03c. is closing > Thu Jun 23 05:22:18 2011 GMT regionserver 10460-0@spock7001:0 [DEBUG] > (regionserver60020.logRoller) org.apache.hadoop.conf.Configuration: > java.io.IOException: config() > > On running status 'detailed' in the shell , I get =3D> > > 0 regionsInTransition > 3 live servers > =A0 spock7001:60020 1308805454136 > =A0 =A0 =A0 =A0requests=3D0, regions=3D0, usedHeap=3D470, maxHeap=3D910 > =A0 =A0spock6002:60020 1308805434201 > =A0 =A0 =A0 =A0requests=3D0, regions=3D1, usedHeap=3D550, maxHeap=3D910 > =A0 =A0 =A0 =A0hbaseTable,,1308805558566.5aefc6c2b9599f55f8b40351a61db03c= . > =A0 =A0 =A0 =A0 =A0 =A0stores=3D1, storefiles=3D2, storefileSizeMB=3D383,= memstoreSizeMB=3D0, > storefileIndexSizeMB=3D1 > =A0 =A0spock6001:60020 1308805268507 > =A0 =A0 =A0 =A0requests=3D0, regions=3D2, usedHeap=3D90, maxHeap=3D910 > =A0 =A0 =A0 =A0-ROOT-,,0 > =A0 =A0 =A0 =A0 =A0 =A0stores=3D1, storefiles=3D1, storefileSizeMB=3D0, m= emstoreSizeMB=3D0, > storefileIndexSizeMB=3D0 > =A0 =A0 =A0 =A0.META.,,1 > =A0 =A0 =A0 =A0 =A0 =A0stores=3D1, storefiles=3D0, storefileSizeMB=3D0, m= emstoreSizeMB=3D0, > storefileIndexSizeMB=3D0 > 0 dead servers > > > I am issuing a checkAndPut() to insert records into HBase. Is this a bug = ? > > Secondly, I have followed the instructions in the HBase book to increase > write throughput. I have the following settings for my hbase table: > > config =3D HBaseConfiguration.create(); > table =3D new HTable (config, "hbaseTable"); > table.setAutoFlush(false); > table.setWriteBufferSize(104857600); > > However, according to my logs, each checkAndPut() call takes on an averag= e > of 5 milliseconds. Is this unavoidable overhead due to locking ? > > All of my HBase daemons are running with -Xmx1g of heapsize. > > Any help is appreciated. > > Thank you, > > Sam >