hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Antonov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-15703) Deadline scheduler needs to return to the client info about skipped calls, not just drop them
Date Mon, 02 May 2016 22:41:12 GMT

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

Mikhail Antonov updated HBASE-15703:
      Resolution: Fixed
    Hadoop Flags: Reviewed
    Release Note: 
With previous deadline mode of RPC scheduling (the implementation in SimpleRpcScheduler, which
is basically a FIFO except that long-running scans are de-prioritized) and FIFO-based RPC
scheduler clients are getting CallQueueTooBigException when RPC call queue is full.

With this patch and when hbase.ipc.server.callqueue.type property is set to "codel" mode,
clients will also be getting CallDroppedException, which means that the request was discarded
by the server as it considers itself to be overloaded and starts to drop requests to avoid
going down under the load. The clients will retry upon receiving this exception. It doesn't
clear MetaCache with region locations.
          Status: Resolved  (was: Patch Available)

Thanks [~eclark]. Pushed to master, branch-1, branch-1.3.

> Deadline scheduler needs to return to the client info about skipped calls, not just drop
> ---------------------------------------------------------------------------------------------
>                 Key: HBASE-15703
>                 URL: https://issues.apache.org/jira/browse/HBASE-15703
>             Project: HBase
>          Issue Type: Bug
>          Components: IPC/RPC
>    Affects Versions: 1.3.0
>            Reporter: Mikhail Antonov
>            Assignee: Mikhail Antonov
>            Priority: Critical
>             Fix For: 1.3.0
>         Attachments: HBASE-15703-branch-1.3.v1.patch, HBASE-15703-branch-1.3.v2.patch
> In AdaptiveLifoCodelCallQueue we drop the calls when we think we're overloaded, we should
instead return CallDroppedException to the cleent or something.

This message was sent by Atlassian JIRA

View raw message