[ https://issues.apache.org/jira/browse/HADOOP-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212789#comment-15212789 ]
ASF GitHub Bot commented on HADOOP-12916: ----------------------------------------- GitHub user xiaoyuyao opened a pull request: https://github.com/apache/hadoop/pull/86 HADOOP-12916 Create a github PR for code review of v04 patch on the JIRA. You can merge this pull request into a Git repository by running: $ git pull https://github.com/xiaoyuyao/hadoop HADOOP-12916 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/hadoop/pull/86.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #86 ---- commit 93cf7377980a69f8b5b22453419a95b58a19c2aa Author: Xiaoyu Yao <x...@apache.org> Date: 2016-03-26T02:45:48Z HADOOP-12916.patch.04 ---- > 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 > > > 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)