hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2551) hadoop-env.sh needs finer granularity
Date Mon, 04 Feb 2008 14:53:07 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565374#action_12565374
] 

Hemanth Yamijala commented on HADOOP-2551:
------------------------------------------

I prefer the first approach of using different variables. This would be easier to provision
through HOD as well. Are there any specific advantages of using the second approach ? (I can
see some, but still... *smile*)

> hadoop-env.sh needs finer granularity
> -------------------------------------
>
>                 Key: HADOOP-2551
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2551
>             Project: Hadoop Core
>          Issue Type: Improvement
>            Reporter: Allen Wittenauer
>            Priority: Minor
>             Fix For: 0.17.0
>
>
> 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.


Mime
View raw message