You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Aleksandr Kovalenko (JIRA)" <ji...@apache.org> on 2013/08/06 13:58:47 UTC
[jira] [Commented] (AMBARI-2814) NameNode HA Wizard: modify
prerequisite checks
[ https://issues.apache.org/jira/browse/AMBARI-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13730682#comment-13730682 ]
Aleksandr Kovalenko commented on AMBARI-2814:
---------------------------------------------
+1 for the patch
> NameNode HA Wizard: modify prerequisite checks
> ----------------------------------------------
>
> Key: AMBARI-2814
> URL: https://issues.apache.org/jira/browse/AMBARI-2814
> Project: Ambari
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Fix For: 1.4.0
>
> Attachments: AMBARI-2814.patch
>
>
> Prerequisite Checks
> When the user clicks on "Enable NameNode HA", we will perform the following checks:
> If the cluster is already secure, display the error message in a popup: "You cannot enable NameNode HA via this wizard as your cluster is already secured. First, disable security by going to Admin > Security, and then run this Enable NameNode HA wizard again. After NameNode HA is enabled, you can go back to Admin > Security to secure the cluster."
> If the above check passes, perform the following checks and display all the errors in one popup:
> If the cluster consists of less than 3 hosts, display the error message is: "You must have at least 3 hosts in your cluster to enable NameNode HA".
> If the cluster consists of less than 3 ZooKeeper Servers, the error message is: "You must have at least 3 ZooKeeper Servers in your cluster to enable NameNode HA".
> If the NameNode is NOT in STARTED state, the error message is: "NameNode must be running before you enable NameNode HA."
> The user cannot proceed forward in case any of the above errors have been encountered.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira