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

Posted to issues@hbase.apache.org by "Ashu Pachauri (JIRA)" <ji...@apache.org> on 2016/02/27 05:40:18 UTC

[jira] [Updated] (HBASE-15354) We should use ClientExceptionUtils#isSpecialException consistently for all operations

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

Ashu Pachauri updated HBASE-15354:
----------------------------------
    Attachment: HBASE-15354-V0.patch

> We should use ClientExceptionUtils#isSpecialException consistently for all operations
> -------------------------------------------------------------------------------------
>
>                 Key: HBASE-15354
>                 URL: https://issues.apache.org/jira/browse/HBASE-15354
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 2.0.0, 1.2.0
>            Reporter: Ashu Pachauri
>            Assignee: Ashu Pachauri
>         Attachments: HBASE-15354-V0.patch
>
>
> Currently we do not clear/update meta cache for some special exceptions if the operation went through AsyncProcess#submit like HTable#put calls. But, we clear meta cache without checking for these special exceptions in case of other operations like gets, deletes etc because they directly go through the RpcRetryingCaller#callWithRetries instead of the AsyncProcess. 



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