[
https://issues.apache.org/jira/browse/YARN-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13897336#comment-13897336
]
Gera Shegalov commented on YARN-1701:
-------------------------------------
{quote}If you think the default path on DFS shouldn't have the
$\{hadoop.log.dir\} as that on local file system, it's another story {quote}.
Seems like we are getting on the same page. it's not another story, it's the
exact reason why I am proposing this change. $\{hadoop.log.dir\} is not a good
idea for a location on HDFS out of the box. I am not aware of a single example
where hadoop.log.dir would refer to an HDFS location. I was using
yarn.nodemanager.remote-app-log-dir=/tmp/logs as an example. But
$\{hadoop.tmp.dir\} defaulting to /tmp/hadoop-$\{user\} is not unreasonable
either.
> 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)