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 2BD0C1159A for ; Thu, 14 Aug 2014 22:45:26 +0000 (UTC) Received: (qmail 89556 invoked by uid 500); 14 Aug 2014 22:45:24 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 89503 invoked by uid 500); 14 Aug 2014 22:45:24 -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 89337 invoked by uid 99); 14 Aug 2014 22:45:24 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Aug 2014 22:45:24 +0000 Date: Thu, 14 Aug 2014 22:45:24 +0000 (UTC) From: "Andrew Purtell (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-11746) checkHBaseAvailable method override {hbase.client.retries.number} configuration to be 1 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-11746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097842#comment-14097842 ] Andrew Purtell commented on HBASE-11746: ---------------------------------------- We want the availability check to quickly and accurately determine if HBase is reachable and up. Seems like that is working as intended according to the description above. The default retry count meant to allow the client to ride over a blip in connectivity wouldn't necessarily be what is desired for a service availability check. > checkHBaseAvailable method override {hbase.client.retries.number} configuration to be 1 > --------------------------------------------------------------------------------------- > > Key: HBASE-11746 > URL: https://issues.apache.org/jira/browse/HBASE-11746 > Project: HBase > Issue Type: Bug > Components: Admin > Affects Versions: 0.98.3, 0.94.22 > Environment: ubuntu machine > Reporter: oren razon > Priority: Minor > Labels: patch > Fix For: 1.0.0, 0.94.23 > > Original Estimate: 24h > Remaining Estimate: 24h > > Hi, > Although my HBase configuration is set for 10 for "hbase.client.retries.number" parameter, the checkHBaseAvailable method in org.apache.hadoop.hbase.client.HBaseAdmin class override this setting and try to connect master with only 1 retry. > This setting cause us to HBase failure when HBase is not available for a sudden moment while checking for availability. Can it use the configured "hbase.client.retries.number" setting instead? -- This message was sent by Atlassian JIRA (v6.2#6252)