[
https://issues.apache.org/jira/browse/HBASE-11332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14046755#comment-14046755
]
Hudson commented on HBASE-11332:
--------------------------------
FAILURE: Integrated in HBase-TRUNK #5245 (See
[https://builds.apache.org/job/HBase-TRUNK/5245/])
HBASE-11332 Fix for metas location cache from HBASE-10785 (enis: rev
14a09e79bdb9b925ce9548b45fc4e26caadaec07)
* hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestHCM.java
*
hbase-client/src/main/java/org/apache/hadoop/hbase/client/ConnectionManager.java
> Fix for metas location cache from HBASE-10785
> ----------------------------------------------
>
> Key: HBASE-11332
> URL: https://issues.apache.org/jira/browse/HBASE-11332
> Project: HBase
> Issue Type: Sub-task
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Fix For: 0.99.0
>
> Attachments:
> 0043-HBASE-11332-Fix-for-metas-location-cache-from-HBASE-.patch,
> hbase-11332_v1.patch
>
>
> In HBASE-10785, we removed the invalidation of the cached location from patch
> v2 to v3. This results in a case where if there is a cached location for
> meta, it is not invalidated.
> Since we do a second check from cache for the location after acquiring the
> lock, this results in metas location to be wrongly cached forever resulting
> in clients blocking indefinitely.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
