ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonenko Alexander (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-18109) After Enabling NNHA, On restarting HDFS, namenodes are stopped
Date Thu, 11 Aug 2016 15:27:20 GMT

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

Antonenko Alexander updated AMBARI-18109:
-----------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed to trunk and 2.4


> 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)

Mime
View raw message