hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15354) Use same criteria for clearing meta cache for all operations
Date Sat, 05 Mar 2016 20:05:40 GMT

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

Sean Busbey commented on HBASE-15354:

unless someone is opposed, I'm fine with this one going into branch-1.2. please release note
the change in behavior.

> 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: Bug
>          Components: Client
>    Affects Versions: 2.0.0, 1.2.0, 1.3.0
>            Reporter: Ashu Pachauri
>            Assignee: Ashu Pachauri
>         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
> 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

View raw message