Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-dev@hadoop.apache.org
Message-ID: <10807036.91471288138339648.JavaMail.jira@thor>
Date: Tue, 26 Oct 2010 20:12:19 -0400 (EDT)
From: "Aaron T. Myers (JIRA)" <jira@apache.org>
To: mapreduce-dev@hadoop.apache.org
Subject: [jira] Created: (MAPREDUCE-2158) Remove need for taskcontroller.cfg
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Remove need for taskcontroller.cfg
----------------------------------

                 Key: MAPREDUCE-2158
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2158
             Project: Hadoop Map/Reduce
          Issue Type: Improvement
          Components: task-controller
    Affects Versions: 0.22.0
            Reporter: Aaron T. Myers
            Assignee: Aaron T. Myers


The taskcontroller.cfg configuration file seems unnecessary. It's parsed by the task-controller binary, and the path to it is baked into that binary at compile-time. It contains only 3 values, none of which are secret, all of which are also specified in either core-site.xml or mapred-site.xml. It seems like getting rid of taskcontroller.cfg will simplify configuration, and have no impact on the security of the system

I suggest we either:

# Pass these values as arguments to task-controller when we execute it.
# Use xerces to enable the task-controller to parse *-site.xml.

Of these two options, I think option 1 seems the cleanest/easiest. Either would be backward-compatible with existing configurations.

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