[jira] Updated: (HADOOP-2551) hadoop-env.sh needs finer granularity

["Raghu Angadi (JIRA)" <ji...@apache.org>]

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

Raghu Angadi updated HADOOP-2551:
---------------------------------

    Attachment: HADOOP-2551.patch

Attached patch handles the following env variables :

HADOOP_NAMENODE_OPTS
HADOOP_SECONDARYNAMENODE_OPTS
HADOOP_DATANODE_OPTS
HADOOP_BALANCER_OPTS
HADOOP_JOBTRACKER_OPTS
HADOOP_TASKTRACKER_OPTS
HADOOP_CLIENT_OPTS

Notes: 
# There is no HADOOP_TASK_OPTS. The tasks are not started by the scripts. If we need it, it needs to be handled inside mapreduce. A different jira might be better.
# As Arun suggested, JobClient and JobShell don't use HADOOP_CLIENT_OPTS
# HADOOP_CLIENT_OPTS applies to any other command that does not have its own variable.

The default options are exactly same as before this patch.



> hadoop-env.sh needs finer granularity
> -------------------------------------
>
>                 Key: HADOOP-2551
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2551
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: scripts
>            Reporter: Allen Wittenauer
>            Assignee: Raghu Angadi
>            Priority: Blocker
>             Fix For: 0.17.0
>
>         Attachments: HADOOP-2551.patch
>
>
> We often configure our HADOOP_OPTS on the name node to have JMX running so that we can do JVM monitoring.  But doing so means that we need to edit this file if we want to run other hadoop commands, such as fsck.  It would be useful if hadoop-env.sh was refactored a bit so that there were different and/or cascading HADOOP_OPTS dependent upon which process/task was being performed.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.