[
https://issues.apache.org/jira/browse/YARN-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13897380#comment-13897380
]
Zhijie Shen commented on YARN-1701:
-----------------------------------
I said it's another story because it's not preventing users from intuitively
enabling AHS. And HDFS is accessed with the default path, isn't it?
I don't think it's a good idea to be distracted by the debate of what's a good
default path. Different people may have different opinions. And as you can see,
it's not AHS only issue. I suggest opening the discussion on what are the good
default path on HDFS and on local FS, and focus on what AHS only issue here, if
you agree.
> 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)
