[
https://issues.apache.org/jira/browse/HBASE-15354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181655#comment-15181655
]
Mikhail Antonov commented on HBASE-15354:
-----------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:checkstyle (default-cli)
on project hbase-testing-util: An error has occurred in Checkstyle report
generation. Failed during checkstyle execution: Unable to process suppressions
file location: hbase/checkstyle-suppressions.xml: Cannot create file-based
resource:invalid distance too far back -> [Help 1]
Doesn't seem legit.
> 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)
