You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Srimanth Gunturi (JIRA)" <ji...@apache.org> on 2014/04/14 07:11:14 UTC

[jira] [Updated] (AMBARI-5455) Ambari configuration for map join conversion and tez container size seems wrong

     [ https://issues.apache.org/jira/browse/AMBARI-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Srimanth Gunturi updated AMBARI-5455:
-------------------------------------

    Attachment: AMBARI-5455.patch

Review at https://reviews.apache.org/r/20303/

> Ambari configuration for map join conversion and tez container size seems wrong
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-5455
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5455
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.5.1
>            Reporter: Srimanth Gunturi
>            Assignee: Srimanth Gunturi
>            Priority: Critical
>             Fix For: 1.5.1
>
>         Attachments: AMBARI-5455.patch
>
>
> For hive:
> hive.auto.convert.join.noconditionaltask.size is set to 1000000000
> - This should be a fraction (1/3) of the container size.
> hive.tez.java.opts has "-Xmx1024m"
> This is different from both map and reduce sizes. Desired values are:
> - map size if map size > 2g else reduce size
> map size is set on the same cluster to ~500mb
> The settings as the are will lead to many failed queries because the mapjoin conversion is to aggressive. If we don't change the container sizes based on cluster configs we will see wide spread problems with containers being killed or perf problems.



--
This message was sent by Atlassian JIRA
(v6.2#6252)