Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.0.0-alpha1
-
None
-
Incompatible change
-
Description
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 |
HADOOP_DN_SECURE_EXTRA_OPTS | HDFS_DATANODE_SECURE_EXTRA_OPTS |
HADOOP_NFS3_SECURE_EXTRA_OPTS | HDFS_NFS3_SECURE_EXTRA_OPTS |
HADOOP_JOB_HISTORYSERVER_OPTS | MAPRED_HISTORYSERVER_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.
Attachments
Attachments
Issue Links
- breaks
-
MAPREDUCE-6904 HADOOP_JOB_HISTORY_OPTS should be HADOOP_JOB_HISTORYSERVER_OPTS in mapred-config.sh
- Resolved
- is required by
-
HADOOP-13365 Convert _OPTS to arrays to enable spaces in file paths
- Resolved
- relates to
-
HADOOP-13595 Rework hadoop_usage to be broken up by clients/daemons/etc.
- Resolved
- links to