[
https://issues.apache.org/jira/browse/AMBARI-11894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14584446#comment-14584446
]
Hudson commented on AMBARI-11894:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #2907 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2907/])
AMBARI-11894. Blueprint export incorrectly removes Oozie heapsize settings from
exported Blueprint. (rnettleton) (rnettleton:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6e5e984b66ad3dd3445e85ca82507daecad43c99)
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
*
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java
> 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
>
> Attachments: AMBARI-11894.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> 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)
