Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <26011913.495701282496297450.JavaMail.jira@thor>
Date: Sun, 22 Aug 2010 12:58:17 -0400 (EDT)
From: "Karthik Ranganathan (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Subject: [jira] Assigned: (HBASE-2931) Do not throw RuntimeExceptions in
 RPC/HbaseObjectWritable code, ensure we log and rethrow as IOE
In-Reply-To: <23517573.477691282338677837.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Karthik Ranganathan reassigned HBASE-2931:
------------------------------------------

    Assignee: Karthik Ranganathan

> Do not throw RuntimeExceptions in RPC/HbaseObjectWritable code, ensure we log and rethrow as IOE
> ------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-2931
>                 URL: https://issues.apache.org/jira/browse/HBASE-2931
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Jonathan Gray
>            Assignee: Karthik Ranganathan
>            Priority: Critical
>             Fix For: 0.90.0
>
>         Attachments: HBASE-2931.patch
>
>
> When there are issues with RPC and HbaseObjectWritable, primarily when server and client have different jars, the only thing that happens is the client will receive an EOF exception.  The server does not log what happened at all and the client does not receive a server trace, rather the server seems to close the connection and the client gets an EOF because it tries to read off of a closed stream.
> We need to ensure that we catch, log, and rethrow as IOE any exceptions that may occur because of an issue with RPC or HbaseObjectWritable.

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