You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrii Tkach (JIRA)" <ji...@apache.org> on 2014/09/09 16:13:28 UTC

[jira] [Commented] (AMBARI-7220) Ambari NN HA wizard cannot detect checkpoint

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

Andrii Tkach commented on AMBARI-7220:
--------------------------------------

+1 for the patch.

> Ambari NN HA wizard cannot detect checkpoint
> --------------------------------------------
>
>                 Key: AMBARI-7220
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7220
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 1.7.0
>            Reporter: Aleksandr Kovalenko
>            Assignee: Aleksandr Kovalenko
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-7220.patch
>
>
> PROBLEM:  When enabling Namenode High Availability in Ambari, at the first step :"run "su -l hdfs -c 'hdfs dfsadmin -safemode enter'" 
> run "su -l hdfs -c 'hdfs dfsadmin -saveNamespace'" "
> Ambari cannot detect the checkpoint has been created and would not allow user to go to next step. 
> BUSINESS IMPACT:   This bug is preventing customer to enable High Availability and customer is not able to avoid the single point of failure of their business. 
> ACTUAL BEHAVIOR:  The "Next Step" button is not available and user cannot go to next step.
> EXPECTED BEHAVIOR:  After creating checkpoint, Ambari should detect the checkpoint and allow user to proceed to the next step.
> SUPPORT ANALYSIS: A possible workaround would be copy the link of checking checkpoint status, and access this link through a different browser.
> The customer use the following steps as a workaround:
> After leaving safe mode manually, then refreshing Ambari and starting wizard again, it say "Checkpoint created" even before entering safe mode again.



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