[jira] [Commented] (HBASE-17449) Add explicit document on different timeout settings

["Yu Li (JIRA)" <ji...@apache.org>]

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

Yu Li commented on HBASE-17449:
-------------------------------

Sorry for the late response, somehow this one was forgotten...

bq. My suggestion is we can first deprecated hbase.client.scanner.timeout.period and introduce two new configs called hbase.rpc.scan.timeout and hbase.regionserver.scanner.ttl. What do you think?
Agreed. I think this will make it clear.

bq. And we should consider what is suitable timeout setting on batch.
I think currently each grouped request is controlled by the hbase.rpc.read/write.timeout settings? Indeed it would be good to have a explicit timeout for batch (without consideration on the implementation efforts)

> Add explicit document on different timeout settings
> ---------------------------------------------------
>
>                 Key: HBASE-17449
>                 URL: https://issues.apache.org/jira/browse/HBASE-17449
>             Project: HBase
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Yu Li
>            Assignee: Yu Li
>            Priority: Critical
>
> Currently we have more than one timeout settings, mainly includes:
> * hbase.rpc.timeout
> * hbase.client.operation.timeout
> * hbase.client.scanner.timeout.period
> And in latest branch-1 or master branch code, we will have two other properties:
> * hbase.rpc.read.timeout
> * hbase.rpc.write.timeout
> However, in current refguid we don't have explicit instruction on the difference of these timeout settings (there're explanations for each property, but no instruction on when to use which)
> In my understanding, for RPC layer timeout, or say each rpc call:
> * Scan (openScanner/next): controlled by hbase.client.scanner.timeout.period
> * Other operations:
>    1. For released versions: controlled by hbase.rpc.timeout
>    2. For 1.4+ versions: read operation controlled by hbase.rpc.read.timeout, write operation controlled by hbase.rpc.write.timeout, or hbase.rpc.timeout if the previous two are not set.
> And hbase.client.operation.timeout is a higher-level control counting retry in, or say the overall control for one user call.
> After this JIRA, I hope when users ask questions like "What settings I should use if I don't want to wait for more than 1 second for a single put/get/scan.next call", we could give a neat answer.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)