You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Aleksandr Kovalenko (JIRA)" <ji...@apache.org> on 2016/08/11 15:11:20 UTC

[jira] [Commented] (AMBARI-18109) After Enabling NNHA, On restarting HDFS, namenodes are stopped

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

Aleksandr Kovalenko commented on AMBARI-18109:
----------------------------------------------

+1 for the patch

> After Enabling NNHA, On restarting HDFS, namenodes are stopped
> --------------------------------------------------------------
>
>                 Key: AMBARI-18109
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18109
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.4.0
>         Environment: ambari-server --hash: 8f9aa197e2195da95497c8acbc2a39c47431cc6a
> Ambari DB: :Oracle
> OS: Debian 7
>            Reporter: Vivek Rathod
>            Assignee: Antonenko Alexander
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-18109.patch
>
>
> STR: 
> -> Enable NNHA
> -> After NNHA is enabled, there will be a restart icon for HDFS services (is it expected)
> -> On restarting services requiring restart (from button on Services page), restart is successful but both the Namenodes are stopped
> We are stopping all DataNodes before starting all services. Instead of stopping all DataNodes, lets stop HDFS service and then start all services.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)