[
https://issues.apache.org/jira/browse/HBASE-18487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-18487:
-----------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 1.2.7
1.5.0
1.3.2
1.4.0
3.0.0
2.0.0
Status: Resolved (was: Patch Available)
To https://git-wip-us.apache.org/repos/asf/hbase.git
abb9d88dce..80b85a857c branch-1 -> branch-1
43e26e5353..6cadd1def7 branch-1.2 -> branch-1.2
c799649a09..8436811026 branch-1.3 -> branch-1.3
16503568e5..2d9dbf27b3 branch-1.4 -> branch-1.4
7bdabed275..f67dae90f9 branch-2 -> branch-2
a5db120e60..422a57223a master -> master
> Minor fixes in row lock implementation
> --------------------------------------
>
> Key: HBASE-18487
> URL: https://issues.apache.org/jira/browse/HBASE-18487
> Project: HBase
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: James Taylor
> Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7
>
> Attachments: HBASE-18487_branch-1.patch, HBASE-18487.patch
>
>
> In reviewing the HRegion.getRowLockInternal() implementation, I noticed a
> couple of possible issues that I wanted to pass along:
> - make sure rowLockContext.cleanUp() always called if row lock could not be
> acquired
> - do not attempt to remove unusable row lock from map multiple times.
> I'll post a patch for consideration.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)