[
https://issues.apache.org/jira/browse/HBASE-6839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469991#comment-13469991
]
Hudson commented on HBASE-6839:
-------------------------------
Integrated in HBase-0.92-security #143 (See
[https://builds.apache.org/job/HBase-0.92-security/143/])
HBASE-6839 correct variable name : mutation should be put (Revision 1388009)
HBASE-6839 Operations may be executed without holding rowLock (Chunhui)
(Revision 1388004)
Result = FAILURE
tedyu :
Files :
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
tedyu :
Files :
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
> Operations may be executed without holding rowLock
> --------------------------------------------------
>
> Key: HBASE-6839
> URL: https://issues.apache.org/jira/browse/HBASE-6839
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Reporter: chunhui shen
> Assignee: chunhui shen
> Priority: Critical
> Fix For: 0.92.3, 0.94.2, 0.96.0
>
> Attachments: HBASE-6839.patch
>
>
> HRegion#internalObtainRowLock will return null if timed out,
> but many place which call this method don't handle this case
> The bad result is operation will be executed even if it havn't obtained the
> row lock. Such as put、delete、increment。。。
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
