You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Enis Soztutar (JIRA)" <ji...@apache.org> on 2015/10/24 04:17:27 UTC
[jira] [Commented] (HBASE-14689) Addendum and unit test for
HBASE-13471
[ https://issues.apache.org/jira/browse/HBASE-14689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972279#comment-14972279 ]
Enis Soztutar commented on HBASE-14689:
---------------------------------------
BTW, HBASE-13896 is also related where the client fails to clear up the meta cache properly. Without a reproducible unit test, it is not clear whether it is really an issue or not.
> Addendum and unit test for HBASE-13471
> --------------------------------------
>
> Key: HBASE-14689
> URL: https://issues.apache.org/jira/browse/HBASE-14689
> Project: HBase
> Issue Type: Bug
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
>
> One of our customers ran into HBASE-13471, which resulted in all the handlers getting blocked and various other issues. While backporting the issue, I noticed that there is one more case where we might go into infinite loop. In case a row lock cannot be acquired (due to a previous leak for example which we have seen in Phoenix before) this will cause similar infinite loop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)