[
https://issues.apache.org/jira/browse/BIGTOP-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056787#comment-14056787
]
Mark Grover commented on BIGTOP-1370:
-------------------------------------
In full disclosure, our conf-empty (the default configuration shipped with our
packages), also uses the relative path for {{/var/log/hadoop-yarn/apps}} but I
don't know of a good way to put hdfs prefix before it because we don't know the
URI/port of namenode in general. Does anyone know if it's possible to somehow
leverage {{fs.defaultFS}} from core-site.xml? What if {{fs.defaultFS}} is not
defined because the users are using the deprected {{fs.default.name}}?
> Update yarn.nodemanager.remote-app-log-dir in hadoop-conf-pseudo to be a URI
> ----------------------------------------------------------------------------
>
> Key: BIGTOP-1370
> URL: https://issues.apache.org/jira/browse/BIGTOP-1370
> Project: Bigtop
> Issue Type: Bug
> Components: hadoop
> Affects Versions: 0.8.0
> Reporter: Mark Grover
>
> In BIGTOP-572, we added file:// as prefix to a few properties to avoid some
> warnings. Along the same lines, we should add an {{hdfs://localhost:8020}}
> prefix to {{/var/log/hadoop-yarn/apps}} (which is the value of
> {{yarn.nodemanager.remote-app-log-dir}} property) in yarn-site.xml
> https://github.com/apache/bigtop/blob/master/bigtop-packages/src/common/hadoop/conf.pseudo/yarn-site.xml#L56
--
This message was sent by Atlassian JIRA
(v6.2#6252)
