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 95714108E4 for ; Thu, 12 Feb 2015 11:47:12 +0000 (UTC) Received: (qmail 78729 invoked by uid 500); 12 Feb 2015 11:47:12 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 78688 invoked by uid 500); 12 Feb 2015 11:47:12 -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 78677 invoked by uid 99); 12 Feb 2015 11:47:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Feb 2015 11:47:12 +0000 Date: Thu, 12 Feb 2015 11:47:12 +0000 (UTC) From: "Andrey Stepachev (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-13022) "RegionException: Retries exhausted..." ERROR in HBaseAdmin.disableTable(...) if hbase.client.pause=0 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-13022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318042#comment-14318042 ] Andrey Stepachev commented on HBASE-13022: ------------------------------------------ Thank you for patch, but why in the first place pause was set to 0? Can you share your usecase where you need zero pause? In my sense code works as expected, with zero pause there will be no pauses between retries and as expected fast fall of retry cycle? This logic used across the code, for example one more place where pause will be zero too org.apache.hadoop.hbase.client.ConnectionUtils#getPauseTime. > "RegionException: Retries exhausted..." ERROR in HBaseAdmin.disableTable(...) if hbase.client.pause=0 > ----------------------------------------------------------------------------------------------------- > > Key: HBASE-13022 > URL: https://issues.apache.org/jira/browse/HBASE-13022 > Project: HBase > Issue Type: Bug > Components: Admin > Reporter: Sergey Smirnov > Attachments: HBASE-13022__RegionException__Retries_exhausted.patch > > > If hbase.client.pause set to 0 it breaks retry back-off logic in HbaseAdmin.getPauseTime() for DDL operations. Operation succeeds because it happens asynchronously but caller get an Exception because caller thread did not wait for operation to complete: > ... > Caused by: org.apache.hadoop.hbase.RegionException: Retries exhausted, it took too long to wait for the table FOO to be disabled. > at org.apache.hadoop.hbase.client.HBaseAdmin.disableTable(HBaseAdmin.java:997) > at org.apache.hadoop.hbase.client.HBaseAdmin.disableTable(HBaseAdmin.java:1005) > ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)