[
https://issues.apache.org/jira/browse/YARN-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394356#comment-15394356
]
Allen Wittenauer commented on YARN-5431:
----------------------------------------
FWIW, I'm planning on making this all consistent in trunk with HADOOP-13341.
HDFS stuff will be:
HDFS_namenode_OPTS, HDFS_datanode_OPTS,etc
YARN stuff will be:
YARN_resourcemanager_OPTS, YARN_nodemanager_OPTS, etc
Effectively:
(capital command)_(subcommand)_OPTS
This means one could do HADOOP_distcp_OPTS, MAPRED_streaming_OPTS,... all in a
consistent way without having custom env var handling all over the place.
> TimeLineReader daemon start should allow to pass its own reader opts
> --------------------------------------------------------------------
>
> Key: YARN-5431
> URL: https://issues.apache.org/jira/browse/YARN-5431
> Project: Hadoop YARN
> Issue Type: Bug
> Components: scripts, timelinereader
> Reporter: Rohith Sharma K S
> Assignee: Rohith Sharma K S
> Fix For: 3.0.0-alpha2
>
> Attachments: YARN-5431.0.patch, YARN-5431.1.patch
>
>
> In yarn script , timelinereader doesn't allow to pass reader_opts.
> {code}
> timelinereader)
> HADOOP_SUBCMD_SUPPORTDAEMONIZATION="true"
> HADOOP_CLASSNAME='org.apache.hadoop.yarn.server.timelineservice.reader.TimelineReaderServer'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
