[
https://issues.apache.org/jira/browse/HADOOP-17280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17200674#comment-17200674
]
Jinglun commented on HADOOP-17280:
----------------------------------
Hi [~tasanuma], thanks your detailed comments ! And your concern makes sense to
me.
{quote}It becomes difficult to promote higher priority queues for users who are
in lower priority queues, and they will be penalized more than expected.
{quote}
Yes the promote would be difficult because the total is smaller. I think this
is good because the service-user would be easier to be scheduled. Because the
highest priority queue doesn't has many calls.
{quote}The RPC costs of service-users will no longer appear in CallValume (Raw
Total incoming Call Volume) metrics.
{quote}
Yes this would be a problem. May be we can add a new metric for service-users?
Since we are trying to guarantee the service quality of service-users, we have
to penalized other users. Otherwise too many the calls would be set the highest
priority then the service-users are not guaranteed anymore. So I think we
should let the other users compete for the left resources.
> Service-user cost shouldn't be accumulated to totalDecayedCallCost and
> totalRawCallCost.
> ----------------------------------------------------------------------------------------
>
> Key: HADOOP-17280
> URL: https://issues.apache.org/jira/browse/HADOOP-17280
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Jinglun
> Assignee: Jinglun
> Priority: Major
> Attachments: HADOOP-17280.001.patch, HADOOP-17280.002.patch
>
>
> HADOOP-17165 has introduced a very useful feature: service-user. After this
> feature I think we shouldn't add the service-user's cost into
> totalDecayedCallCost and totalRawCallCost anymore. Because it may give all
> the identities the priority 0(Supposing we have a big service-user).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
