Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AB21F9F2B for ; Tue, 25 Dec 2012 04:40:16 +0000 (UTC) Received: (qmail 65724 invoked by uid 500); 25 Dec 2012 04:40:15 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 65508 invoked by uid 500); 25 Dec 2012 04:40:15 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 65381 invoked by uid 99); 25 Dec 2012 04:40:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Dec 2012 04:40:14 +0000 Date: Tue, 25 Dec 2012 04:40:14 +0000 (UTC) From: "gavin peng (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-7433) org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed 1 action: servers with issues: slave3.hadoop:60020 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-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gavin peng updated HBASE-7433: ------------------------------ Summary: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed 1 action: servers with issues: slave3.hadoop:60020 (was: Caused by: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed 1 action: servers with issues: slave3.hadoop:60020) > org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed 1 action: servers with issues: slave3.hadoop:60020 > ------------------------------------------------------------------------------------------------------------------------------- > > Key: HBASE-7433 > URL: https://issues.apache.org/jira/browse/HBASE-7433 > Project: HBase > Issue Type: Bug > Components: Balancer, regionserver > Affects Versions: 0.94.1 > Environment: linux ,hbase0.94.1 ,hadoop1.0.3,zookeeper3.4.3 > Reporter: gavin peng > Priority: Blocker > Labels: balance, regionserver > Original Estimate: 193h > Remaining Estimate: 193h > > when i use the client of kettler insert data into hbase table by put operator,it is no problem when the table only has one region,but the data is also too much,so i want to load balancing,so i created many region when i created the table,this time problem is producted,exception is follow: > Problem inserting row into HBase: Failed 1 action: servers with issues: slave2.hadoop:60020, > at org.pentaho.di.trans.steps.hbaseoutput.HBaseOutput.processRow(HBaseOutput.java:316) > at org.pentaho.di.trans.step.RunThread.run(RunThread.java:50) > at java.lang.Thread.run(Unknown Source) > Caused by: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed 1 action: servers with issues: slave2.hadoop:60020, > at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchCallback(HConnectionManager.java:1601) > org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatch(HConnectionManager.java:1377) > at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:916) > at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:772) > at org.apache.hadoop.hbase.client.HTable.put(HTable.java:747) > at org.pentaho.hbase.shim.common.CommonHBaseConnection.executeTargetTablePut(CommonHBaseConnection.java:732) > at org.pentaho.di.trans.steps.hbaseoutput.HBaseOutput.processRow(HBaseOutput.java:307) > we know the client find the rowkey belong to the region of the table,but can't connection the regionserver.but the regionserver is ok,but not running gc > so i can't understand the problem,please help me ,thanks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira