[
https://issues.apache.org/jira/browse/HADOOP-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277342#comment-15277342
]
Xiaoyu Yao commented on HADOOP-12916:
-------------------------------------
[~kihwal], the end to end rpc response time includes the queueing time and the
processing time. The namesystem lock wait time is counted as part of the the
processing time. Can you elaborate on "It may not work correctly for
namenode?". Thanks!
> Allow RPC scheduler/callqueue backoff using response times
> ----------------------------------------------------------
>
> Key: HADOOP-12916
> URL: https://issues.apache.org/jira/browse/HADOOP-12916
> Project: Hadoop Common
> Issue Type: Improvement
> Components: ipc
> Reporter: Xiaoyu Yao
> Assignee: Xiaoyu Yao
> Fix For: 2.8.0
>
> Attachments: HADOOP-12916.00.patch, HADOOP-12916.01.patch,
> HADOOP-12916.02.patch, HADOOP-12916.03.patch, HADOOP-12916.04.patch,
> HADOOP-12916.05.patch, HADOOP-12916.06.patch, HADOOP-12916.07.patch,
> HADOOP-12916.08.patch
>
>
> Currently back off policy from HADOOP-10597 is hard coded to base on whether
> call queue is full. This ticket is open to allow flexible back off policies
> such as moving average of response time in RPC calls of different priorities.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
