You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Siddharth Wagle (JIRA)" <ji...@apache.org> on 2013/08/15 03:50:47 UTC
[jira] [Updated] (AMBARI-2905) SNAMENODE should not start at HA
cluster
[ https://issues.apache.org/jira/browse/AMBARI-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Wagle updated AMBARI-2905:
------------------------------------
Attachment: AMBARI-2905.patch
When ambari server restarts we put all SCH in UNKNOWN state. This allows the Heartbeat handler to move SNN from maintenance to INSTALLED.
> SNAMENODE should not start at HA cluster
> ----------------------------------------
>
> Key: AMBARI-2905
> URL: https://issues.apache.org/jira/browse/AMBARI-2905
> Project: Ambari
> Issue Type: Bug
> Components: controller
> Affects Versions: 1.4.0
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Fix For: 1.4.0
>
> Attachments: AMBARI-2905.patch
>
>
> Currently, in HA NN cluster, starting HDFS service at services tab, tries to start SNAMENODE as well (through it is in Maintainance state because of executing {code}curl -u admin:admin -i -X PUT -d '{"RequestInfo":{"context":"SNN maintenance"},"Body":{"HostRoles":{"state":"MAINTENANCE"}}}' http://$SERVER:8080/api/v1/clusters/$CLUSTER/hosts/$SNN_HOST/host_components/SECONDARY_NAMENODE
> {code} command )
--
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