hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-13341) Deprecate HADOOP_SERVERNAME_OPT; replace with HADOOP_(command)_OPT
Date Tue, 05 Jul 2016 06:24:10 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-13341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Allen Wittenauer updated HADOOP-13341:
--------------------------------------
    Description: 
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.

  was:
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.


> 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
>
> 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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message