[
https://issues.apache.org/jira/browse/HADOOP-13341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15367731#comment-15367731
]
Allen Wittenauer commented on HADOOP-13341:
-------------------------------------------
One of the unexpected challenges here is ordering of operations:
* HADOOP\_OPTS
* HADOOP\_(command)\_OPTS
* HADOOP\_CLIENTS\_OPTS
... is likely the ideal. But the way HADOOP_CLIENT_OPTS are appended makes
this particularly tricky since it is done in the case statements. It might be
better to pull that code out first, then deal with the various daemons.
> Deprecate HADOOP_SERVERNAME_OPT; replace with HADOOP_(command)_OPT
> ------------------------------------------------------------------
>
> Key: HADOOP-13341
> URL: https://issues.apache.org/jira/browse/HADOOP-13341
> Project: Hadoop Common
> Issue Type: Improvement
> Components: scripts
> Affects Versions: 3.0.0-alpha1
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
>
> Big features like YARN-2928 demonstrate that even senior level Hadoop
> developers forget that daemons need a custom _OPT env var. We can replace
> all of the custom vars with generic handling just like we do for the username
> check.
> For example, today:
> HADOOP_NAMENODE_OPT
> would become
> HADOOP_namenode_OPT
> But if I wanted custom distcp options, there is no equivalent. But if the
> command replacement mode was, then
> HADOOP_distcp_OPT
> would automatically work.
> In the case of YARN-2928, HADOOP_timelinereaderserver_OPT would automatically
> be checked without any extra work on behalf of the contributors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
