[
https://issues.apache.org/jira/browse/TEZ-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979760#comment-14979760
]
Hitesh Shah edited comment on TEZ-2914 at 10/29/15 3:57 AM:
------------------------------------------------------------
bq. Even with capacity scheduler and hierarchical queues, with the level of
multi-tenancy we have within a queue one single job that runs very wide can end
up hogging resources and starve other jobs in the queue.
Should have clarified. When I mentioned cluster resource cap, I meant to imply
the max. cluster resources a single Tez app can use regardless of whether YARN
can give it more resources.
was (Author: hitesh):
bq. Even with capacity scheduler and hierarchical queues, with the level of
multi-tenancy we have within a queue one single job that runs very wide can end
up hogging resources and starve other jobs in the queue.
Should have clarified. When I mentioned cluster resource cap, I meant to imply
the max. cluster resources a single Tez app can use.
> Ability to limit vertex concurrency
> -----------------------------------
>
> Key: TEZ-2914
> URL: https://issues.apache.org/jira/browse/TEZ-2914
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Jonathan Eagles
> Assignee: Bikas Saha
>
> Add equivalent functionality of *MAPREDUCE-5583. Ability to limit running map
> and reduce tasks* in tez
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
