hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15866) Split hbase.rpc.timeout into *.read.timeout and *.write.timeout
Date Fri, 05 Aug 2016 19:19:20 GMT

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

Hadoop QA commented on HBASE-15866:

| (x) *{color:red}-1 overall{color}* |
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 4s {color} | {color:red}
HBASE-15866 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/0.2.1/precommit-patchnames
for help. {color} |
|| Subsystem || Report/Notes ||
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12822357/read-write-rpc-timeouts-edited.v2.patch
| JIRA Issue | HBASE-15866 |
| Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/2966/console |
| Powered by | Apache Yetus 0.2.1   http://yetus.apache.org |

This message was automatically generated.

> Split hbase.rpc.timeout into *.read.timeout and *.write.timeout
> ---------------------------------------------------------------
>                 Key: HBASE-15866
>                 URL: https://issues.apache.org/jira/browse/HBASE-15866
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Andrew Purtell
>            Assignee: Vivek Koppuru
>              Labels: newbie, patch
>             Fix For: 2.0.0
>         Attachments: HBASE-15866.patch, read-write-rpc-timeouts-edited.v2.patch, read-write-rpc-timeouts.patch
> We have a single tunable for the RPC timeout interval - hbase.rpc.timeout. This is fine
for the general case but there are use cases where it would be advantageous to set two separate
timeouts for reads (gets, scans, perhaps with significant server side filtering - although
the new scanner heartbeat feature mitigates where available) and mutations (fail fast under
tight SLA, resubmit or take mitigating action). 
> I propose we refer to a configuration setting "hbase.rpc.read.timeout" when handling
read operations and "hbase.rpc.write.timeout" when handling write operations. If those values
are not set in the configuration, fall back to the value of "hbase.rpc.timeout" or its default.

> So for example in HTable instead of one global timeout for each RPC (rpcTimeout), there
would be a readRpcTimeout and writeRpcTimeout also set up in HTable#finishSetup. Then wherever
we set up RPC with RpcRetryingCallerFactory#newCaller(int rpcTimeout) we pass in the read
or write timeout depending on what the op is.
> In general I don't like the idea of adding configuration parameters to our already heavyweight
set, but I think the inability to control timeouts separately for reads and writes is an operational
> See also PHOENIX-2916.

This message was sent by Atlassian JIRA

View raw message