[
https://issues.apache.org/jira/browse/AMBARI-15871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15241624#comment-15241624
]
Goutam Tadi commented on AMBARI-15871:
--------------------------------------
Hi [~rlevas],
I am facing this issue when APP Timeline Server (ATS) is installed on a node
where no other component like HDFS_Client or DataNode are installed.
In this case hdfs keytab is not copied to this node, hence ATS fails on this
keytab availability.
I tried adding hdfs keytab identity at YARN service level and APP Timeline
Server component level, but of no use. Can you please look in to this issue ?
Thanks.
> App Timeline Server start fails on a kerberized cluster due to absence of
> hdfs keytab
> -------------------------------------------------------------------------------------
>
> Key: AMBARI-15871
> URL: https://issues.apache.org/jira/browse/AMBARI-15871
> Project: Ambari
> Issue Type: Bug
> Components: stacks
> Affects Versions: 2.2.2
> Reporter: Goutam Tadi
> Assignee: Goutam Tadi
> Priority: Blocker
> Fix For: 2.2.2
>
>
> Kerberizing a cluster with App timeline server (not collocated with
> HDFS-client) fails to restart service since it fails to obtain hdfs headless
> keytab. This is because the hdfs keytabs are generated on Namenodes and hdfs
> client nodes but not on App Timeline Server nodes. A small fix in Yarn
> kerberos.json can get rid off this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
