[
https://issues.apache.org/jira/browse/HBASE-22434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16848850#comment-16848850
]
binlijin commented on HBASE-22434:
----------------------------------
[~xucang]
{quote}
If there is no exception found, it returns true and causes clear cache action.
Is this the real intention?
{quote}
I just keep the behave just like before.
{quote}
Can this be cleant up a bit?
we can do something like
{quote}
OK.
I add TimeoutIOException and CallTimeoutException to specialException set, so
it will not clean meta cache when this exception happen, so my patch reduce
meta clean which different from before.
> Improve clear meta cache
> ------------------------
>
> Key: HBASE-22434
> URL: https://issues.apache.org/jira/browse/HBASE-22434
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 2.2.0
> Reporter: binlijin
> Assignee: binlijin
> Priority: Major
> Attachments: HBASE-22434-master-v2.patch,
> HBASE-22434-master-v3.patch, HBASE-22434-master-v4.patch,
> cleanServerCache.jpg, cleanServerCache2.jpg
>
>
> 2.2.0 clear meta cache more aggressive and give more load to meta region,
> need to improve the clear logic. This is relate to the
> AsyncRequestFutureImpl#cleanServerCache logic.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
