ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandor Magyari (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-21067) Atlas config values not getting populated on BP cluster install with strategy : "NEVER_APPLY"
Date Fri, 19 May 2017 07:08:04 GMT

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

Sandor Magyari updated AMBARI-21067:
------------------------------------
    Status: Patch Available  (was: Open)

> Atlas config values not getting populated on BP cluster install with strategy : "NEVER_APPLY"
> ---------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-21067
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21067
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Sandor Magyari
>            Assignee: Sandor Magyari
>            Priority: Critical
>             Fix For: 3.0.0, 2.5.2
>
>
> After cluster install, the following 5 ATLAS's 'application-properties' configs are empty:

> {code}
> atlas.graph.index.search.solr.zookeeper-url 
> atlas.graph.storage.hostname 
> atlas.kafka.bootstrap.servers 
> atlas.kafka.zookeeper.connect 
> atlas.audit.hbase.zookeeper.quorum
> {code}
> BlueprintConfigProcessor should configure these properties in case there's no stack advisor
strategy set.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message