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

Janus Chow edited comment on HADOOP-17165 at 10/27/20, 4:00 AM:
----------------------------------------------------------------

In our case, users submit jobs to Presto, and "presto" is the unified account 
to contact NameNode.

When users submit some bad jobs, "presto" becomes the bad user and consumes 
most of the resources of the queue. If we add "presto" as the service account, 
and the requests from "presto" are always in the highest priority queue, then 
the normal users are still suffering the congestion.

I think the idea of this patch is based on the suppose that all service 
accounts are obeying the law, but some are not.


was (Author: symious):
In our case, users submit jobs to Presto, and "presto" is the unified account 
to contact NameNode.

When users submit some bad jobs, "presto" becomes the bad user and consumes 
most of the resources of the queue. If we add "presto" as the service account, 
and the requests from "presto" are always in the highest priority queue, then 
the normal users are still suffering the congesting.

I think the idea of this patch is based on the suppose that all service 
accounts are obeying the law, but some are not.

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

Reply via email to