incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Wagle (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-2905) SNAMENODE should not start after transition to Maintenance mode
Date Thu, 15 Aug 2013 01:56:47 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Siddharth Wagle updated AMBARI-2905:
------------------------------------

    Summary: SNAMENODE should not start after transition to Maintenance mode  (was: SNAMENODE
should not start at HA cluster)
    
> SNAMENODE should not start after transition to Maintenance mode
> ---------------------------------------------------------------
>
>                 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

Mime
View raw message