[ https://issues.apache.org/jira/browse/HBASE-15354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181596#comment-15181596 ]
Hudson commented on HBASE-15354: -------------------------------- FAILURE: Integrated in HBase-Trunk_matrix #757 (See [https://builds.apache.org/job/HBase-Trunk_matrix/757/]) HBASE-15354 Same criteria to clear metacache across operations (Ashu (antonov: rev 27cf0c8c365b61fe12a9e85422e30d1f217f6b7b) * hbase-client/src/main/java/org/apache/hadoop/hbase/client/RegionAdminServiceCallable.java * hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestMetaCache.java * hbase-client/src/main/java/org/apache/hadoop/hbase/client/RegionServerCallable.java > 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)