You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrew Onischuk (JIRA)" <ji...@apache.org> on 2015/06/09 15:01:00 UTC
[jira] [Created] (AMBARI-11811) Oozie crashes after start on
blueprint install
Andrew Onischuk created AMBARI-11811:
----------------------------------------
Summary: 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
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)