[ https://issues.apache.org/jira/browse/HBASE-6170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401810#comment-13401810 ]
Hadoop QA commented on HBASE-6170: ---------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12533555/HBASE-6170v2.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 6 new or modified tests. +1 hadoop2.0. The patch compiles against the hadoop 2.0 profile. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 6 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hbase.regionserver.TestAtomicOperation org.apache.hadoop.hbase.security.access.TestAccessController Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/2266//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2266//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2266//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/2266//console This message is automatically generated. > Timeouts for row lock and scan should be separate > ------------------------------------------------- > > Key: HBASE-6170 > URL: https://issues.apache.org/jira/browse/HBASE-6170 > Project: HBase > Issue Type: Improvement > Components: regionserver > Affects Versions: 0.94.0 > Reporter: Otis Gospodnetic > Assignee: Chris Trezzo > Priority: Minor > Fix For: 0.96.0 > > Attachments: HBASE-6170v1.patch, HBASE-6170v1.patch, > HBASE-6170v1.patch, HBASE-6170v2.patch > > > Apparently the timeout used for row locking and for scanning is global. It > would be better to have two separate timeouts. > (opening the issue to make Lars George happy) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira