ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Nettleton (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-11894) Blueprint export incorrectly removes Oozie heapsize settings from exported Blueprint
Date Fri, 12 Jun 2015 20:27:01 GMT

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

Robert Nettleton updated AMBARI-11894:
--------------------------------------
    Attachment: AMBARI-11894.patch

Uploaded initial version of patch. 

> 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)

Mime
View raw message