You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Mahadev konar (JIRA)" <ji...@apache.org> on 2014/08/06 01:39:12 UTC

[jira] [Reopened] (AMBARI-6709) After Namenode is moved via Ambari the hive metastore namenode hostname is not updated with the new namenode hostname

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

Mahadev konar reopened AMBARI-6709:
-----------------------------------


> After Namenode is moved via Ambari the hive metastore namenode hostname is not updated with the new namenode hostname
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-6709
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6709
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.6.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>             Fix For: 1.7.0
>
>
> The NameNode was moved using the "move" button in Ambari to a different host. After this hive jobs were failing as the hive metastore refers to the old hostname for namenode. (This is not a problem in a HA enabled cluster)
> Steps to reproduce:
> - Bring up a 4 node cluster which includes hive
> - create sample hive tables
> - move the namenode through ambari
> - run /usr/lib/hive/bin/metatool -listFSRoot
> - It will list the old namenode host



--
This message was sent by Atlassian JIRA
(v6.2#6252)