hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesse Yates (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6170) Timeouts for row lock and scan should be separate
Date Tue, 26 Jun 2012 23:01:44 GMT

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

Jesse Yates commented on HBASE-6170:
------------------------------------

Minor note: ints seem to be sufficient for basically all the use cases that I've heard of
(24 days scanner timeout/lease timeout seems massive). Using ints over longs here is a nice
space savings (though relatively trivial, bits count with GC). 
                
> 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

        

Mime
View raw message