[
https://issues.apache.org/jira/browse/AMBARI-18131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424482#comment-15424482
]
Oleg Nechiporenko commented on AMBARI-18131:
--------------------------------------------
{noformat}
Error: JAVA_HOME is not defined correctly.
We cannot execute /home/hudson/tools/java/latest1.7/bin/java
{noformat}
> UI - atlas.rest.address needs to be recalculated by StackAdvisor whenever
> AtlasServer is added/moved/deleted
> ------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-18131
> URL: https://issues.apache.org/jira/browse/AMBARI-18131
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Alejandro Fernandez
> Assignee: Oleg Nechiporenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-18131.patch
>
>
> Similar to Zookeeper Quorum, if the topology of Atlas Servers changes (move,
> delete, add), then Stack Advisor needs to recalculate atlas.rest.address
> property in atlas-application.properties
> The value is a csv of http(s):$server:$port for each Atlas Server.
> Today, the configuration files can only specify config-to-config
> dependencies, so there is no config-to-component dependency.
> This means that today the UI has config initializers to make changes to
> properties like hbase.zookeeper.quorum and nimbus.seeds
> Is this feasible in Ambari 2.4? Once this is done, we need to prevent the UI
> from editing atlas.rest.address after the cluster is deployed, since only
> Stack Advisor will allow calculating the value, so we may need the correct
> values for editable-only-at-install, overridable, read-only in the config
> file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
