hbase-issues mailing list archives

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

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

Hadoop QA commented on HBASE-15354:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 4s {color} | {color:red}
HBASE-15354 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/latest/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12791581/HBASE-15354-V5.patch
|
| JIRA Issue | HBASE-15354 |
| Powered by | Apache Yetus 0.1.0   http://yetus.apache.org |
| Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/851/console |


This message was automatically generated.



> 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
(v6.3.4#6332)

Mime
View raw message