[
https://issues.apache.org/jira/browse/HADOOP-17165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17223321#comment-17223321
]
Janus Chow commented on HADOOP-17165:
-------------------------------------
[~csun] Thanks for the reply.
I think _refreshCallQueue_ is a good choice for reloading the parameters since
it is creating a new RpcScheduler and FairCallQueue inside.
After rereading the document in HADOOP-15016, one concern comes to me is that
users may misuse the service-user config and they may create a lot of
service-users causing many separate queues created in FairCallQueue.
> Implement service-user feature in DecayRPCScheduler
> ---------------------------------------------------
>
> Key: HADOOP-17165
> URL: https://issues.apache.org/jira/browse/HADOOP-17165
> Project: Hadoop Common
> Issue Type: New Feature
> Reporter: Takanobu Asanuma
> Assignee: Takanobu Asanuma
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0
>
> Attachments: HADOOP-17165.001.patch, HADOOP-17165.002.patch,
> after.png, before.png
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> In our cluster, we want to use FairCallQueue to limit heavy users, but not
> want to restrict certain users who are submitting important requests. This
> jira proposes to implement the service-user feature that the user is always
> scheduled high-priority queue.
> According to HADOOP-9640, the initial concept of FCQ has this feature, but
> not implemented finally.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
