[ 
https://issues.apache.org/jira/browse/HBASE-6170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401981#comment-13401981
 ] 

Hudson commented on HBASE-6170:
-------------------------------

Integrated in HBase-TRUNK #3079 (See 
[https://builds.apache.org/job/HBase-TRUNK/3079/])
    HBASE-6170 Timeouts for row lock and scan should be separate (Chris Trezzo) 
(Revision 1354325)

     Result = SUCCESS
tedyu : 
Files : 
* 
/hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/client/ClientScanner.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/Leases.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestScannerTimeout.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/coprocessor/TestCoprocessorInterface.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java

                
> 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: 6170v4.patch, HBASE-6170v1.patch, HBASE-6170v1.patch, 
> HBASE-6170v1.patch, HBASE-6170v2.patch, HBASE-6170v3.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

        

Reply via email to