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 Sat, 19 Mar 2016 01:10:33 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.01.patch

Thanks for [~szetszwo] for the review. I've update the patch that addresses your comments
and the checkstyle/findbugs issues from Jenkins.

bq. "Should priorityLevels be passed in the second try/catch in CallQueueManager#createScheduler?"


We already pass the int.class which is the priority level in the second try/catch. 

> 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
>
>
> 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)

Mime
View raw message