hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo Nicholas Sze (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12916) Allow different Hadoop IPC Call Queue throttling policies with FCQ/BackOff
Date Sat, 19 Mar 2016 22:03:33 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202987#comment-15202987
] 

Tsz Wo Nicholas Sze commented on HADOOP-12916:
----------------------------------------------

Thanks for the update.  I think averageResponseTimeInLastWindow and callCountInLastWindow
probably need to be declared with AtomicLongArray and AtomicDoubleArray since we also need
to synchronize individual values in the arrays.  Patch looks good other than that.

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