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

Posted to mapreduce-dev@hadoop.apache.org by "Iyappan Srinivasan (JIRA)" <ji...@apache.org> on 2009/09/24 06:50:16 UTC

[jira] Created: (MAPREDUCE-1032) taskcontroller.cfg should be checked before task tracker comes up

taskcontroller.cfg should be checked before task tracker comes up
-----------------------------------------------------------------

                 Key: MAPREDUCE-1032
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1032
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: contrib/capacity-sched
    Affects Versions: 0.22.0
            Reporter: Iyappan Srinivasan


Right now, task-controller.cfg should have two mandatory parameters mapreduce.cluster.local.dir and hadoop.log.dir, without which cluster comes up including Task tracker , but when any jobs are submitted, it gives errors. 

This will highly confuse the Ops and end-user.

Even though, when every job is submitted, task-controller.cfg is checked, it should be checked in the very beginning when Task tracker comes up. 

Expected behaviour is :
1) TT should not come up.
2) TT logs should show why its not come up like which parameter is missing and if found, if the values mismatches with the mapred-site.xml



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