You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Alejandro Fernandez (JIRA)" <ji...@apache.org> on 2016/09/14 23:44:20 UTC

[jira] [Updated] (AMBARI-18394) Blueprint-deployed cluster with NameNode HA out-of-the-box fails when starting Namenode during EU/RU

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

Alejandro Fernandez updated AMBARI-18394:
-----------------------------------------
    Component/s: blueprints

> Blueprint-deployed cluster with NameNode HA out-of-the-box fails when starting Namenode during EU/RU
> ----------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-18394
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18394
>             Project: Ambari
>          Issue Type: Bug
>          Components: blueprints
>    Affects Versions: 2.2.2
>            Reporter: Alejandro Fernandez
>             Fix For: trunk
>
>
> STR:
> * Use Blueprints to deploy cluster with NameNode HA out-of-the-box
> * Attempt an EU/RU
> The problem is that during a Blueprint deployment, it keeps the following 2 configs in hadoop-env
> dfs_ha_initial_namenode_active
> dfs_ha_initial_namenode_standby
> When it's time to perform an EU/RU (or start NN in general), then it thinks that NameNode HA is still not complete.
> Blueprint with HA out of the box needs a step to delete these configs after the deployment is done.



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