[
https://issues.apache.org/jira/browse/TEZ-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15063318#comment-15063318
]
Bikas Saha commented on TEZ-2914:
---------------------------------
bq. if (vInfo.concurrency >= vInfo.concurrencyLimit) {
We will come here only if the limit was > 0 to start with.
The design deliberately ignores internal vertex logic (including speculation).
Everything will run as is but only be bottlenecked here. This also releases
attempts in the order in which they arrived. So there will be no change in
scheduling order with/without this. If speculation is scheduled and is within
limits then we will speculate (I think we should because the reasons for both
are orthogonal). If the vertex schedules a speculation after the normal
attempts then it will continue to remain in that order.
> 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
> Attachments: TEZ-2914.1.patch
>
>
> 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)
