You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Antonenko Alexander (JIRA)" <ji...@apache.org> on 2015/10/20 19:00:30 UTC

[jira] [Commented] (AMBARI-13492) NN HA wizard gets stuck when JournalNodes fail after getting started

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

Antonenko Alexander commented on AMBARI-13492:
----------------------------------------------

+1 for the patch

> NN HA wizard gets stuck when JournalNodes fail after getting started
> --------------------------------------------------------------------
>
>                 Key: AMBARI-13492
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13492
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.1.3
>            Reporter: Aleksandr Kovalenko
>            Assignee: Aleksandr Kovalenko
>            Priority: Critical
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-13492.patch
>
>
> Attempting to enable NameNode HA, and the wizard is stuck at initializing shared edits when the JournalNodes are not running. The HA wizard does start the JNs, but if they stop for some reason, the wizard is stuck without any message. The reason the wizard is stuck is that it relies on JN's JMX response which is not available
> {code}
>   "metrics" : {
>     "dfs" : {
>       "journalnode" : {
>         "journalsStatus" : "{\"myha\":{\"Formatted\":\"true\"}}",
> {code}
> When this is not available we should tell user why wizard has a disabled Next button.



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