You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Mikhail Antonov (JIRA)" <ji...@apache.org> on 2016/03/04 06:06:40 UTC

[jira] [Updated] (HBASE-15390) ClientExceptionUtils doesn't handle CallQueueTooBigException properly

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

Mikhail Antonov updated HBASE-15390:
------------------------------------
    Description: 
In #isMetaClearingException() we're checking for CallQueueTooBigException, but under debugger in tests I saw that what we're really getting in here is RemoteWithExtrasException, which doesn't allow to easily unwrap CQTBE from it, since it's stored in the classname field, and findException() or unwrapRemoteException() fail to unwrap it correctly.

I think we'd have the same behavior with other

  was:In #isMetaClearingException() we're checking for CallQueueTooBigException, but under debugger in tests I saw that what we're really getting in here here is RetriesWithExtrasException, which doesn't allow to easily unwrap CQTBE from it, since it's stored in the classname field, and findException() or unwrapRemoteException() fail to unwrap it correctly.


> ClientExceptionUtils doesn't handle CallQueueTooBigException properly
> ---------------------------------------------------------------------
>
>                 Key: HBASE-15390
>                 URL: https://issues.apache.org/jira/browse/HBASE-15390
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 1.2.0
>            Reporter: Mikhail Antonov
>            Assignee: Mikhail Antonov
>             Fix For: 1.2.1
>
>
> In #isMetaClearingException() we're checking for CallQueueTooBigException, but under debugger in tests I saw that what we're really getting in here is RemoteWithExtrasException, which doesn't allow to easily unwrap CQTBE from it, since it's stored in the classname field, and findException() or unwrapRemoteException() fail to unwrap it correctly.
> I think we'd have the same behavior with other



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)