ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-8764) Configs: Check tez.runtime.io.sort.mb and io.sort.mb to not set above 2G for current releases.
Date Wed, 17 Dec 2014 19:09:13 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-8764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14250328#comment-14250328
] 

Hudson commented on AMBARI-8764:
--------------------------------

FAILURE: Integrated in Ambari-trunk-Commit-docker #513 (See [https://builds.apache.org/job/Ambari-trunk-Commit-docker/513/])
AMBARI-8764. Configs: Check tez.runtime.io.sort.mb and io.sort.mb to not set above 2G for
current releases. (aonishuk) (aonishuk: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9a6110a3a76f04b3764f7170d1b7644eb441a9ca)
* ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py


> Configs: Check tez.runtime.io.sort.mb and io.sort.mb to not set above 2G for current
releases.
> ----------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-8764
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8764
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.0.0
>
>
> PROBLEM:
> Current versions as of up to HDP 2.2.0, io.sort.mb and tez.runtime.io.sort.mb
> above 2GB is not supported. Ambari currently calculates these to be around
> 30-40% of the container size, may result in higher than 2GB setting, this
> causes job failures.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message