hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ming Ma (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-10597) RPC Server signals backoff to clients when all request queues are full
Date Thu, 23 Apr 2015 22:42:40 GMT

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

Ming Ma updated HADOOP-10597:
    Release Note: This change introduces a new configuration key used by RPC server to decide
whether to send backoff signal to RPC Client when RPC call queue is full. When the feature
is enabled, RPC server will no longer block on the processing of RPC requests when RPC call
queue is full. It helps to improve quality of service when the service is under heavy load.
The configuration key is in the format of "ipc.#port#.backoff.enable" where #port# is the
port number that RPC server listens on. For example, if you want to enable the feature for
the RPC server that listens on 8020, set ipc.8020.backoff.enable to true.

> RPC Server signals backoff to clients when all request queues are full
> ----------------------------------------------------------------------
>                 Key: HADOOP-10597
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10597
>             Project: Hadoop Common
>          Issue Type: Sub-task
>            Reporter: Ming Ma
>            Assignee: Ming Ma
>             Fix For: 2.8.0
>         Attachments: HADOOP-10597-2.patch, HADOOP-10597-3.patch, HADOOP-10597-4.patch,
HADOOP-10597-5.patch, HADOOP-10597-6.patch, HADOOP-10597.patch, MoreRPCClientBackoffEvaluation.pdf,
> Currently if an application hits NN too hard, RPC requests be in blocking state, assuming
OS connection doesn't run out. Alternatively RPC or NN can throw some well defined exception
back to the client based on certain policies when it is under heavy load; client will understand
such exception and do exponential back off, as another implementation of RetryInvocationHandler.

This message was sent by Atlassian JIRA

View raw message