Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 9 Jun 2015 14:53:00 +0000 (UTC)
From: "Andrew Onischuk (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12836537.1433854824000.28753.1433861580752@Atlassian.JIRA>
In-Reply-To: <JIRA.12836537.1433854824000@Atlassian.JIRA>
References: <JIRA.12836537.1433854824000@Atlassian.JIRA>
 <JIRA.12836537.1433854824180@arcas>
Subject: [jira] [Updated] (AMBARI-11811) Oozie crashes after start on
 blueprint install
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Onischuk updated AMBARI-11811:
-------------------------------------
    Description: 
Oozie is thinking that heapsize is in kb and failing with too low
heapsize.


  was:
This happens because some properties which show capacity don't have 'm'
appended when installing via blueprints (via UI installs it is done by UI)
this results in Oozie thinking that heapsize is in kb and failing with too low
heapsize.

Also there are some other properties which don't have 'm' appended, but should
have, which results in missconfiguration issues (instead on megabytes
kilobytes are set)

The proposal on how to fix it is to dynamically find the properties with
unit=MB and append 'm' to them, rather than hardcode that properties like it
is done now.


> Oozie crashes after start on blueprint install
> ----------------------------------------------
>
>                 Key: AMBARI-11811
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11811
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.1.0
>
>
> Oozie is thinking that heapsize is in kb and failing with too low
> heapsize.


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