You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Hitesh Shah (JIRA)" <ji...@apache.org> on 2016/03/16 21:24:33 UTC
[jira] [Commented] (TEZ-3168) Provide a more predictable approach
for total resource guidance for wave/split calculation
[ https://issues.apache.org/jira/browse/TEZ-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198088#comment-15198088 ]
Hitesh Shah commented on TEZ-3168:
----------------------------------
[~vinodkv] [~jianhe] Mind taking a look at this patch to see whether we are using the APIs for queue and cluster resources correctly. Also, if we are accidentally using any private APIs, let us know.
> Provide a more predictable approach for total resource guidance for wave/split calculation
> -------------------------------------------------------------------------------------------
>
> Key: TEZ-3168
> URL: https://issues.apache.org/jira/browse/TEZ-3168
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Hitesh Shah
> Assignee: Hitesh Shah
> Attachments: TEZ-3168.wip.patch
>
>
> Currently, Tez uses headroom for checking total available resources. This is flaky as it ends up causing the split count to be determined by a point in time lookup at what is available in the cluster. A better approach would be either the queue size or even cluster size to get a more predictable count.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)