[
https://issues.apache.org/jira/browse/HADOOP-16224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16807003#comment-16807003
]
Erik Krogen edited comment on HADOOP-16224 at 4/1/19 5:21 PM:
--------------------------------------------------------------
I originally created this JIRA focusing on the reservation support, but
realized that this didn't align with my [original
proposal|https://issues.apache.org/jira/browse/HADOOP-15016?focusedCommentId=16673288&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16673288],
so updated the summary/description to reflect that this JIRA should be for the
cost-based portion.
fyi [~ywskycn], [~xyao] who were originally involved with HADOOP-15016
was (Author: xkrogen):
Please see Section 2.2 of the [initial design
document|https://issues.apache.org/jira/secure/attachment/12902423/Adding%20reservation%20support%20to%20NameNode%20RPC%20resource_v2.pdf]
posted to HADOOP-15016 for more details on the proposed design.
fyi [~ywskycn], [~xyao] who were originally involved with HADOOP-15016
> Cost-Based RPC FairCallQueue
> ----------------------------
>
> Key: HADOOP-16224
> URL: https://issues.apache.org/jira/browse/HADOOP-16224
> Project: Hadoop Common
> Issue Type: Improvement
> Components: ipc
> Reporter: Erik Krogen
> Assignee: Christopher Gregorian
> Priority: Major
> Labels: qos, rpc
>
> HADOOP-15016 initially described extensions to the Hadoop FairCallQueue
> encompassing both cost-based analysis of incoming RPCs, as well as support
> for reservations of RPC capacity for system/platform users. This JIRA intends
> to track the former, as HADOOP-15016 was repurposed to more specifically
> focus on the reservation portion of the work.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
