You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2010/08/23 00:23:16 UTC

[jira] Resolved: (HBASE-2931) Do not throw RuntimeExceptions in RPC/HbaseObjectWritable code, ensure we log and rethrow as IOE

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

stack resolved HBASE-2931.
--------------------------

    Hadoop Flags: [Reviewed]
      Resolution: Fixed

Applied to TRUNK.  Thanks for the patch Karthik.

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