[
https://issues.apache.org/jira/browse/YARN-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394115#comment-15394115
]
Varun Saxena commented on YARN-5431:
------------------------------------
[~rohithsharma], I would prefer to name the opts as
{{YARN_TIMELINEREADER_OPTS}} instead of {{HADOOP_TIMELINEREADER_OPTS}} along
the lines of YARN_RESOURCEMANAGER_OPTS.
Ideally HADOOP_NODEMANAGER_OPTS should also be named as YARN_NODEMANAGER_OPTS
and so on. I see in YARN-1400 only RM opts were changed but not others.
Also should we have better description for these OPTS along the lines of
{{yarn-env.sh}} ?
But these issues are not related to this JIRA and a separate JIRA can be filed
for it...
Moreover, timelinereader command is meant only for ATSv2 and timelineserver
only for ATSv1/1.5 (i.e. depending on timeline service version you are running)
This isn't very clear from the help. Maybe we can handle this here itself. cc
[~sjlee0]
> 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
