[
https://issues.apache.org/jira/browse/HADOOP-17165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17221312#comment-17221312
]
Janus Chow commented on HADOOP-17165:
-------------------------------------
Yes, we are implementing the impersonate solution, but the Presto case is just
an example of the bad use of service-user.
If all service-users can use the impersonate solution, there wouldn't be a need
for this patch to deal with service-users.
What I was trying to say is that when the service-user can not use the
impersonate solution, but it's sending a lot of requests that are not really
important, and with this patch, the performance of the server wouldn't be
improved.
> 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]
