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-20402) Assign Slaves and Clients page displays incorrect configuration unless a change is made in Assign Masters page
Date Thu, 16 Mar 2017 00:58:43 GMT

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

Hudson commented on AMBARI-20402:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7052 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7052/])
AMBARI-20402: Assign Slaves and Clients page displays incorrect (sangeetar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=55dc8ac9224366c0fd08d03da42176652a146ce0])
* (edit) ambari-web/app/mixins/wizard/assign_master_components.js


> Assign Slaves and Clients page displays incorrect configuration unless a change is made
in Assign Masters page
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-20402
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20402
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.5.0
>            Reporter: Sangeeta Ravindran
>            Assignee: Sangeeta Ravindran
>             Fix For: trunk, 2.5.0
>
>         Attachments: AMBARI-20402.patch, AMBARI-20402_trunk.patch, AssignSlavesAndClients_AfterChanges.jpg,
AssignSlavesAndClients_BeforeChanges.jpg
>
>
> 1. On a multi-node cluster (for e.g. 5-node cluster), run the ambari install wizard.
> 2. Do not change defaults and navigate to Step 6 (Assign Slaves and Clients). 
> 3. The recommended configuration does not seem to be place the components well. For e.g.,
DataNodes are recommended on all 5 nodes. (see AssignSlavesAndClients_BeforeChanges.jpg).
> 4. Navigate back to Step 5 (Assign Masters). Make a change. For e.g. move the Atlas Metadata
Server to a different host. Next, change it back to the original host so that in effect nothing
has changed.
> 5. Now move to Step 6 again and see that the configuration has changed and seems more
in line with best practices although effectively nothing has changed in the Assign Masters
page. (see AssignSlavesAndClients_AfterChanges.jpg)



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

Mime
View raw message