[
https://issues.apache.org/jira/browse/AMBARI-7048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14112952#comment-14112952
]
Hudson commented on AMBARI-7048:
--------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #50 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/50/])
AMBARI-7048. Change component message from "cannot" to "should not" (sgunturi:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f23e09de6c9aad0523c3fa77e2eaf7bfda72a5cc)
* ambari-server/src/main/resources/stacks/HDP/1.3.2/services/stack_advisor.py
* ambari-server/src/test/python/stacks/2.0.6/common/test_stack_advisor.py
* ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py
> Change component message from "cannot" to "should not"
> ------------------------------------------------------
>
> Key: AMBARI-7048
> URL: https://issues.apache.org/jira/browse/AMBARI-7048
> Project: Ambari
> Issue Type: Task
> Components: controller
> Affects Versions: 1.7.0
> Reporter: Srimanth Gunturi
> Assignee: Srimanth Gunturi
> Fix For: 1.7.0
>
> Attachments: AMBARI-7048.patch
>
>
> When check master component assignment and trying to put NN and SNN on same
> host, I get the following warning:
> "NameNode and Secondary NameNode cannot be hosted on same machine"
> Since this is a warning, should we re-phrase to:
> "NameNode and Secondary NameNode should not be hosted on same machine"
--
This message was sent by Atlassian JIRA
(v6.2#6252)
