ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Speidel (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-8226) Exported Blueprint doesn't have configs [[nimbus.childopts, supervisor.childopts, worker.childopts]] in config group storm-site
Date Sat, 08 Nov 2014 01:35:33 GMT
John Speidel created AMBARI-8226:
------------------------------------

             Summary: Exported Blueprint doesn't have configs [[nimbus.childopts, supervisor.childopts,
worker.childopts]] in config group storm-site 
                 Key: AMBARI-8226
                 URL: https://issues.apache.org/jira/browse/AMBARI-8226
             Project: Ambari
          Issue Type: Bug
          Components: blueprints
    Affects Versions: 1.7.0
            Reporter: John Speidel
            Assignee: John Speidel
             Fix For: 1.7.0


In some cases, configuration properties that are marked as topology properties  in the blueprint
config processor, contain 'undefined' instead of an actual hostname.  

The three properties mentioned in the summary fall into this category if storm is deployed
without Ganglia.

For example, here is the value of nimbus.childopts:
"-Xmx1024m -Djava.security.auth.login.config=/etc/storm/conf/storm_jaas.conf -javaagent:/usr/lib/storm/contrib/storm-jmxetric/lib/jmxetric-1.0.4.jar=host=undefined,port=8649,wireformat31x=true,mode=multicast,config=/usr/lib/storm/contrib/storm-jmxetric/conf/jmxetric-conf.xml,process=Nimbus_JVM"

Because the BP processor didn't match any cluster host to a portion of the property value,
it determined that this property must point to an external host and doesn't export the property.




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

Mime
View raw message