[
https://issues.apache.org/jira/browse/YARN-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13896345#comment-13896345
]
Zhijie Shen commented on YARN-1701:
-----------------------------------
Hm... Now I understand your problem. I used to think AHS was unable to write
into HDFS on your machine.
W.R.T the default path, the convention across xxxx-default.xml is have some
${xxx.dir} prefix. What bothers you here is what you have in HADOOP_LOG_DIR is
the default location in HDFS for history files. However, it's not wrong. If
HADOOP_LOG_DIR=/tmp on your machine, you might be more comfortable with the
path. right? Anyway, you can change the path to whatever makes sense to you.
> More intuitive defaults for AHS
> -------------------------------
>
> Key: YARN-1701
> URL: https://issues.apache.org/jira/browse/YARN-1701
> Project: Hadoop YARN
> Issue Type: Sub-task
> Affects Versions: 2.4.0
> Reporter: Gera Shegalov
> Assignee: Gera Shegalov
> Attachments: YARN-1701.v01.patch
>
>
> When I enable AHS via yarn.ahs.enabled, the app history is still not visible
> in AHS webUI. This is due to NullApplicationHistoryStore as
> yarn.resourcemanager.history-writer.class. It would be good to have just one
> key to enable basic functionality.
> yarn.ahs.fs-history-store.uri uses {code}${hadoop.log.dir}{code}, which is
> local file system location. However, FileSystemApplicationHistoryStore uses
> DFS by default.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)