ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-18131) UI - atlas.rest.address needs to be recalculated by StackAdvisor whenever AtlasServer is added/moved/deleted
Date Wed, 17 Aug 2016 15:53:21 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-18131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424765#comment-15424765
] 

Hudson commented on AMBARI-18131:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5541 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5541/])
AMBARI-18131. UI - atlas.rest.address needs to be recalculated by (onechiporenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=42fd20de03c0c665b5659f47b758eabc7681e3bd])
* (edit) ambari-web/app/controllers/wizard/step7_controller.js
* (edit) ambari-web/test/utils/configs/config_initializer_test.js
* (edit) ambari-web/app/utils/configs/config_initializer.js


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

Mime
View raw message