[ https://issues.apache.org/jira/browse/HBASE-14689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Enis Soztutar updated HBASE-14689: ---------------------------------- Attachment: hbase-14689-after-revert.patch > 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 > Fix For: 2.0.0, 1.2.0, 1.3.0, 1.0.3, 1.1.3, 0.98.16 > > Attachments: hbase-14689-after-revert.patch, > hbase-14689-after-revert.patch, hbase-14689_v1-branch-1.1.patch, > hbase-14689_v1-branch-1.1.patch, 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)