You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Robert Nettleton (JIRA)" <ji...@apache.org> on 2015/06/12 22:12:02 UTC
[jira] [Created] (AMBARI-11894) Blueprint export incorrectly
removes Oozie heapsize settings from exported Blueprint
Robert Nettleton created AMBARI-11894:
-----------------------------------------
Summary: Blueprint export incorrectly removes Oozie heapsize settings from exported Blueprint
Key: AMBARI-11894
URL: https://issues.apache.org/jira/browse/AMBARI-11894
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.1.0
Reporter: Robert Nettleton
Assignee: Robert Nettleton
Priority: Critical
Fix For: 2.1.0
The Blueprint processor incorrectly removes some Oozie heapsize settings that are defined in the "oozie-env" configuration type.
Steps to reproduce:
1. Deploy a single-node cluster with Ambari UI with HDFS, Yarn, and Oozie.
2. Use the REST API to export a Blueprint from this running cluster;
http://host:port/api/v1/clusters/clusterone?format=blueprint
The following properties, normally included in "oozie-env", are not present in the exported Blueprint:
"oozie_heapsize"
"oozie_permsize"
I'm working on a fix for this issue, and will be submitting a patch shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)