[
https://issues.apache.org/jira/browse/HADOOP-10597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14508048#comment-14508048
]
Arpit Agarwal edited comment on HADOOP-10597 at 4/22/15 10:39 PM:
------------------------------------------------------------------
+1 for the v6 patch. Reviewed the test case and it looks like Steve's comment
was addressed. Thanks Ming.
I'll commit this by tomorrow.
was (Author: arpitagarwal):
+1 for the updated patch. Reviewed the test case and it looks like Steve's
comment was addressed. Thanks Ming.
I'll commit this by tomorrow.
> Evaluate if we can have RPC client back off when server is under heavy load
> ---------------------------------------------------------------------------
>
> 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
> 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,
> RPCClientBackoffDesignAndEvaluation.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
(v6.3.4#6332)
