Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1797277681.1205345206251.JavaMail.jira@brutus>
Date: Wed, 12 Mar 2008 11:06:46 -0700 (PDT)
From: "Bryan Duxbury (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-506) When an exception has to escape
 ServerCallable due to exhausted retries, show all the exceptions that lead
 to this situation
In-Reply-To: <961390185.1205281246251.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577957#action_12577957 ] 

Bryan Duxbury commented on HBASE-506:
-------------------------------------

I ran TestEmptyMetaInfo against this patch now that it's committed, and it works fine.

> When an exception has to escape ServerCallable due to exhausted retries, show all the exceptions that lead to this situation
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-506
>                 URL: https://issues.apache.org/jira/browse/HBASE-506
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: client
>            Reporter: Bryan Duxbury
>            Assignee: Bryan Duxbury
>             Fix For: 0.1.0, 0.2.0
>
>         Attachments: 506-0.1.patch, 506.patch
>
>
> Every so often, we find ourselves trying to debug a problem that happens in HTable where we exhaust all our retries trying to contact the region server hosting the region we want to operate on. Oftentimes the last exception that comes out is something like WrongRegionException, which should just never be the case. 
> As a way to improve our debugging capabilities, when we decide to throw an exception out of ServerCallable, let's show not just the last exception but all the exceptions that caused all the retries in the first place. This will help us understand the sequence of events that led to us running out of retries. 

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