Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1150418200.1210611295731.JavaMail.jira@brutus>
Date: Mon, 12 May 2008 09:54:55 -0700 (PDT)
From: "Raghu Angadi (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-2551) hadoop-env.sh needs finer
 granularity
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Raghu Angadi commented on HADOOP-2551:
--------------------------------------

Yes, HAEAPSIZE is not part of this jira. There was no mention of removing any existing variable. 

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