[
https://issues.apache.org/jira/browse/HBASE-15354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Antonov updated HBASE-15354:
------------------------------------
Resolution: Fixed
Fix Version/s: 1.2.1
Release Note:
This patch fixes some issues when MetaCache (region location cache) gets
unnecessarily dropped on the client.
On master branch we now in RegionServerCallable and RegionServerAdminCallable
pass the actual exception down to Connection#updateCachedLocation, so we could
check there if the exception is "meta-clearing" or not.
on branch-1, branch-1.2 and branch 1.3 we now check if the exception is
meta-clearing or not in AsyncProcess (this check was there on master, but not
on earlier branches)
Status: Resolved (was: Patch Available)
> 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
> 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)
