Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 5 Oct 2012 04:33:49 +1100 (NCT)
From: "Phabricator (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <1900807920.896.1349372029963.JavaMail.jiratomcat@arcas>
In-Reply-To: <1805994537.164291.1349339227665.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HBASE-6943) [89-fb] Do not catch certain
 exceptions trying to get an RS connection
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Phabricator commented on HBASE-6943:
------------------------------------

Kannan has added CCs to the revision "[jira] [HBASE-6943] [89-fb] Do not catch certain exceptions trying to get an RS connection".
Added CCs: avf, adela, pritamdamania, aaiyer, nspiegelberg, amirshim, mycnyc

  Let's try to cc individually until we can figure out how to more easily email the group automatically.

REVISION DETAIL
  https://reviews.facebook.net/D5877

To: Kannan, Liyin, Karthik, JIRA, mbautin
Cc: avf, adela, pritamdamania, aaiyer, nspiegelberg, amirshim, mycnyc

                
> [89-fb] Do not catch certain exceptions trying to get an RS connection
> ----------------------------------------------------------------------
>
>                 Key: HBASE-6943
>                 URL: https://issues.apache.org/jira/browse/HBASE-6943
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Mikhail Bautin
>         Attachments: D5877.1.patch
>
>
> When getting a regionserver connection in 0.89-fb in HBaseClient, we catch all types of Throwable. I have observed a real case when the client looked stuck. On debugging it turned out that a NoSuchMethodError was thrown and caught, leaving the connection in an inconsistent state (initialized socket but null streams). All following attempts resulted in NPEs that were also caught, and no errors were logged. From the user's perspective the client was just stuck. The root cause was the absence of a required jar (hence the NoSuchMethodError) but it was not reported properly.

--
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