hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16285) Drop RPC requests if it must be considered as timeout at client
Date Thu, 11 Aug 2016 03:00:26 GMT

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

Hudson commented on HBASE-16285:

FAILURE: Integrated in HBase-1.3-IT #790 (See [https://builds.apache.org/job/HBase-1.3-IT/790/])
HBASE-16285 Drop RPC requests if it must be considered as timeout at (zhangduo: rev 974dab0f03c5e3db3234a7425c532157b660b10e)
* hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestHCM.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcServer.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcServerInterface.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/CallRunner.java

> Drop RPC requests if it must be considered as timeout at client
> ---------------------------------------------------------------
>                 Key: HBASE-16285
>                 URL: https://issues.apache.org/jira/browse/HBASE-16285
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 2.0.0, 1.3.0, 1.4.0
>            Reporter: Phil Yang
>            Assignee: Phil Yang
>             Fix For: 2.0.0, 1.3.0, 1.4.0
>         Attachments: HBASE-16285-branch-1-v1.patch, HBASE-16285-branch-1-v2.patch, HBASE-16285-branch-1-v3.patch,
HBASE-16285-branch-1-v4.patch, HBASE-16285-branch-1-v5.patch, HBASE-16285-branch-1-v5.patch,
HBASE-16285-branch-1-v6.patch, HBASE-16285-v1.patch, HBASE-16285-v2.patch, HBASE-16285-v3.patch,
HBASE-16285-v4.patch, HBASE-16285-v5.patch, HBASE-16285-v6.patch, HBASE-16285-v7.patch, HBASE-16285-v7.patch,
HBASE-16285-v8.patch, HBASE-16285-v9.patch
> After HBASE-15593, we have a timeout param in header of RPC requests. We can use it in
more scenes.
> A straightforward scene is to drop requests if it has waited so long in RPC queue and
has been dropped by client. Even if we handle this request and send the response back, it
will not be used any more. And client may have sent a retry. In an extreme case, if the server
is slow, all requests may be timeout or queue-full-exception because we should handle previous
requests which have been dropped by client and many resources at server are wasted.

This message was sent by Atlassian JIRA

View raw message