[jira] [Updated] (HBASE-6170) Timeouts for row lock and scan should be separate

["Chris Trezzo (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-6170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Trezzo updated HBASE-6170:
--------------------------------

    Attachment: HBASE-6170v1.patch

Attached is a first patch for this issue.

I have added two config parameters (and associated defaults) in HConstants:
HBASE_REGIONSERVER_ROWLOCK_TIMEOUT_PERIOD
HBASE_CLIENT_SCANNER_TIMEOUT_PERIOD

Now, each lease in Leases.java can specify their own timeout period. If no timeout period is specified, the original HBASE_REGIONSERVER_LEASE_PERIOD_KEY parameter is used as default.

I ran the TestScannerTimeout tests and everything passed. I will submit the patch and get a QA run.

Comments are welcome.

Thanks,
Chris
                
> 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
>            Priority: Minor
>             Fix For: 0.96.0
>
>         Attachments: HBASE-6170v1.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