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 "Philip Zeyliger (JIRA)" <ji...@apache.org> on 2011/03/14 02:57:29 UTC

[jira] Created: (MAPREDUCE-2381) JobTracker instrumentation not consistent about error handling

JobTracker instrumentation not consistent about error handling
--------------------------------------------------------------

                 Key: MAPREDUCE-2381
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2381
             Project: Hadoop Map/Reduce
          Issue Type: Improvement
            Reporter: Philip Zeyliger
         Attachments: MAPREDUCE-2381.patch.txt

In the current code, if the class specified by the JobTracker instrumentation config property is not there, the JobTracker fails to start with a ClassNotFound.  If it's there, but it can't load for whatever reason, the JobTracker continues with the default.  Having two different error-handling routes is a bit confusing; I propose to move one line so that it's consistent.  (On the TaskTracker instrumentation side, if any of the multiple instrumentations aren't available, the default is used.)

The attached patch merely moves a line inside of the try block that's already there. 

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