Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <806519455.17801270750896705.JavaMail.jira@brutus.apache.org>
Date: Thu, 8 Apr 2010 18:21:36 +0000 (UTC)
From: "Jean-Daniel Cryans (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Resolved: (HBASE-2417) HCM.locateRootRegion fails hard on
 "Connection refused"
In-Reply-To: <378973175.48531270663234402.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Daniel Cryans resolved HBASE-2417.
---------------------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]

Committed to branch, branch pre-durab, and trunk. Stack reviewed the patch with me.

> HCM.locateRootRegion fails hard on "Connection refused"
> -------------------------------------------------------
>
>                 Key: HBASE-2417
>                 URL: https://issues.apache.org/jira/browse/HBASE-2417
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.20.3
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.20.4, 0.21.0
>
>         Attachments: HBASE-2417-v2.patch, HBASE-2417.patch
>
>
> While running some tests on replication, I saw that our client does something dumb if it tries to contact a dead region server that held the ROOT region in HCM.locateRootRegion. Will post stack trace in a comment.
> The problem here is that we don't retry at all, the exception will come straight out of HCM like it's the end of the world.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.