You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Tom White (JIRA)" <ji...@apache.org> on 2011/03/02 18:25:37 UTC

[jira] Commented: (HADOOP-7098) tasktracker property not set in conf/hadoop-env.sh

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

Tom White commented on HADOOP-7098:
-----------------------------------

+1 The lack of a HADOOP_TASKTRACKER_OPTS definition looks like an oversight (these variables were introduced in HADOOP-2551). HADOOP_TASKTRACKER_OPTS is already honoured by bin/mapred, so no changes are needed there.

Bernd, have you tested this manually? There's currently no easy way to write an automated test for this change.

> tasktracker property not set in conf/hadoop-env.sh
> --------------------------------------------------
>
>                 Key: HADOOP-7098
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7098
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 0.20.2, 0.21.1, 0.22.0
>            Reporter: Bernd Fondermann
>            Assignee: Bernd Fondermann
>         Attachments: hadoop-7098.patch
>
>
> For all cluster components, except TaskTracker the OPTS environment variable is set like this in hadoop-env.sh:
> export HADOOP_<COMPONENT>_OPTS="-Dcom.sun.management.jmxremote $HADOOP_<COMPONENT>_OPTS"
> The provided patch fixes this.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira