[
https://issues.apache.org/jira/browse/YARN-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138184#comment-14138184
]
Zhijie Shen commented on YARN-2565:
-----------------------------------
[~karams], I think you've neglected mentioning the config:
yarn.timeline-service.generic-application-history.enabled. It should be true,
such that FileSystemApplicationHistoryStore is picked by
RMApplicationHistoryWriter, which cannot access HDFS correctly in secure mode.
After YARN-2033, when you enable generic history service, you should by default
pick the new storage stack based on TimelineStore. The problem seems to be that
the configurations which determine what store is chosen by
ApplicationHistoryServer and RMApplicationHistoryWriter is not consistent. On
RMApplicationHistoryWriter side, we should also use
FileSystemApplicationHistoryStore only when users have explicitly put it in the
config file.
> ResourceManager is fails to start when GenericHistoryService is enabled in
> secure mode without doing manual kinit as yarn
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-2565
> URL: https://issues.apache.org/jira/browse/YARN-2565
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager, timelineserver
> Affects Versions: 2.6.0
> Environment: Secure cluster with ATS (timeline server enabled) and
> yarn.resourcemanager.system-metrics-publisher.enabled=true
> so that RM can send Application history to Timeline Store
> Reporter: Karam Singh
> Assignee: Zhijie Shen
>
> Observed that RM fails to start in Secure mode when GenericeHistoryService is
> enabled and ResourceManager is set to use Timeline Store
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
