You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Elliott Clark (JIRA)" <ji...@apache.org> on 2015/10/24 19:23:27 UTC

[jira] [Comment Edited] (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=14972751#comment-14972751 ] 

Elliott Clark edited comment on HBASE-14689 at 10/24/15 5:23 PM:
-----------------------------------------------------------------

*edit*
+1 looks good to me


was (Author: eclark):
I don't think that you should remove the throw on line 2957. That will mask which error is being hit.

> 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
>         Attachments: hbase-14689_v1.patch
>
>
> 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)