hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiaoyu Yao (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-12916) Allow different Hadoop IPC Call Queue throttling policies with FCQ/BackOff
Date Tue, 29 Mar 2016 05:21:25 GMT

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

Xiaoyu Yao updated HADOOP-12916:
    Attachment: HADOOP-12916.05.patch

Thanks [~arpitagarwal] and [~szetszwo] for the review. 
Update the patch that 
1) Fixing exception handling when constructing the scheduler instance.
2) Keep the default decay factor and decay windows size to the same as the original FCQ.
3) Enable decay on the average response time for scheduler decision.

I don't change the Configuration#getTimeDurations() to return a List because it incurs extra
box/unbox overhead. A long array should be good for many cases.

> Allow different Hadoop IPC Call Queue throttling policies with FCQ/BackOff
> --------------------------------------------------------------------------
>                 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
>         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
> 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

View raw message