[
https://issues.apache.org/jira/browse/AMBARI-18109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417645#comment-15417645
]
Hudson commented on AMBARI-18109:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #5508 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5508/])
AMBARI-18109. After Enabling NNHA, On restarting HDFS, namenodes are (hiveww:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cb96d5389406d9bb435e465cc670d07e16aa9526])
*
ambari-web/app/controllers/main/admin/highAvailability/nameNode/step9_controller.js
* ambari-web/app/messages.js
> 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)
