[MAPREDUCE-2381] JobTracker instrumentation not consistent about error handling

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.23.0
• Hadoop Flags: Reviewed
• Assignee: Philip Martin
• Reporter: Philip Martin
• Created: 14/Mar/11 01:56
• Updated: 15/Nov/11 00:48
• Resolved: 18/May/11 18:54

Description

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.