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/04/14 20:37:25 UTC

[jira] [Updated] (HBASE-15354) Use same criteria for clearing meta cache for all operations

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

Mikhail Antonov updated HBASE-15354:
------------------------------------
    Issue Type: Sub-task  (was: Bug)
        Parent: HBASE-15654

> Use same criteria for clearing meta cache for all operations
> ------------------------------------------------------------
>
>                 Key: HBASE-15354
>                 URL: https://issues.apache.org/jira/browse/HBASE-15354
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client
>    Affects Versions: 2.0.0, 1.2.0, 1.3.0
>            Reporter: Ashu Pachauri
>            Assignee: Ashu Pachauri
>             Fix For: 1.2.1
>
>         Attachments: HBASE-15354-V0.patch, HBASE-15354-V1.patch, HBASE-15354-V2.patch, HBASE-15354-V3.patch, HBASE-15354-V4.patch, HBASE-15354-V5.patch, HBASE-15354-v5-addendum.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)