[
https://issues.apache.org/jira/browse/HADOOP-13341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Wang updated HADOOP-13341:
---------------------------------
Target Version/s: 3.0.0-alpha2 (was: 3.0.0-alpha1)
> Deprecate HADOOP_SERVERNAME_OPTS; replace with (command)_(subcommand)_OPTS
> --------------------------------------------------------------------------
>
> 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 _OPTS env var. We can replace
> all of the custom vars with generic handling just like we do for the username
> check.
> For example, with generic handling in place:
> || Old Var || New Var ||
> | HADOOP_NAMENODE_OPTS | HDFS_namenode_OPTS |
> | YARN_RESOURCEMANAGER_OPTS | YARN_resourcemanager_OPTS |
> | n/a | YARN_timelinereader_OPTS |
> | n/a | HADOOP_distcp_OPTS |
> | n/a | MAPRED_distcp_OPTS |
> This makes it:
> a) consistent across the entire project
> b) consistent for every subcommand
> c) eliminates almost all of the custom appending in the case statements
> It's worth pointing out that subcommands like distcp that sometimes need a
> higher than normal client-side heapsize or custom options are a huge win.
> Combined with .hadooprc and/or dynamic subcommands, it means users can easily
> do customizations based upon their needs without a lot of weirdo shell
> aliasing or one line shell scripts off to the side.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
