You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2013/07/16 02:14:51 UTC
[jira] [Commented] (HBASE-6170) Timeouts for row lock and scan
should be separate
[ https://issues.apache.org/jira/browse/HBASE-6170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709232#comment-13709232 ]
Hudson commented on HBASE-6170:
-------------------------------
SUCCESS: Integrated in HBase-TRUNK #4256 (See [https://builds.apache.org/job/HBase-TRUNK/4256/])
HBASE-8909. HBASE-6170 broke hbase.regionserver.lease.period config, we should support it for BC (add missing file) (enis: rev 1503488)
* /hbase/trunk/hbase-common/src/test/java/org/apache/hadoop/hbase/TestHBaseConfiguration.java
HBASE-8909. HBASE-6170 broke hbase.regionserver.lease.period config, we should support it for BC (enis: rev 1503484)
* /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ClientScanner.java
* /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/HBaseConfiguration.java
* /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java
* /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.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.95.0
>
> Attachments: 6170.add2, 6170.addendum, 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
For more information on JIRA, see: http://www.atlassian.com/software/jira