You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Bikas Saha (JIRA)" <ji...@apache.org> on 2013/10/28 18:24:32 UTC
[jira] [Resolved] (TEZ-585) Unify code path for reused and new
containers
[ https://issues.apache.org/jira/browse/TEZ-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bikas Saha resolved TEZ-585.
----------------------------
Resolution: Fixed
Fix Version/s: 0.2.0
> Unify code path for reused and new containers
> ---------------------------------------------
>
> Key: TEZ-585
> URL: https://issues.apache.org/jira/browse/TEZ-585
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Bikas Saha
> Fix For: 0.2.0
>
> Attachments: TEZ-585.1.patch, TEZ-585.2.patch
>
>
> Without this there is a race between new and reused containers for task assignments. It is not correct to assign a task to a rack-local new container if there is a rack-local reused container that can also be matched. Unifying the assignment logic can help prevent this systematically.
> This also sets us up to trade-off rack-local reused container vs node-local new container if we want to do that.
--
This message was sent by Atlassian JIRA
(v6.1#6144)