hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3747) [replication] ReplicationSource should differanciate remote and local exceptions
Date Thu, 07 Apr 2011 04:52:05 GMT

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

stack commented on HBASE-3747:
------------------------------

+1

> [replication] ReplicationSource should differanciate remote and local exceptions
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-3747
>                 URL: https://issues.apache.org/jira/browse/HBASE-3747
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.90.1
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>            Priority: Minor
>             Fix For: 0.90.3
>
>         Attachments: HBASE-3747.patch
>
>
> From Jeff Whiting on the list:
> I'm not sure...the key to everything was realizing picking up on RemoteException in "Unable
to replicate because org.apache.hadoop.ipc.RemoteException" and realizing that it was on the
replication cluster.
> If it said something like "Unable to replicate. Destination cluster threw an exception:
org.apache.hadoop.ipc.RemoteException: java.io.IOException: java.lang.RuntimeException:"
> Or something that makes it clear it is an exception on the remote or destination cluster
would be helpful.  It is easy to scan over org.apache.hadoop.ipc.RemoteException and read
it like "org.ap...some-kind-of...exception."

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message