ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Foley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14455) After changing the hostname on the HA cluster the ZKFC's metadata still uses old hostname.
Date Wed, 10 Feb 2016 22:45:18 GMT

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

Matt Foley commented on AMBARI-14455:
-------------------------------------

Also, if Kerberos is enabled, the above procedure needs to be preceded by
{code}
0. If Kerberos security is enabled, disable it using the Ambari Web > Admin > Kerberos
> Disable Kerberos button.
{code}
and followed by
{code}
If Kerberos security is desired, then:
12. Enable Kerberos security by working through either the Automated or Manual setup documented
in the Ambari Security Guide.  In either process, new service keytabs will have to be generated
and deployed with the new hostnames.
{code}

> After changing the hostname on the HA cluster the ZKFC's metadata still uses old hostname.
> ------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-14455
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14455
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.0
>            Reporter: Irina Easterling
>            Assignee: Vitaly Brodetskyi
>             Fix For: 2.2.1
>
>
> After changing the hostname to be new on the HA cluster the ZKFC's metadata still uses
old hostname.



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

Mime
View raw message