[OOZIE-2024] Confusing message when a job can't be looked up by JavaActionExecutor

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 4.0.0
• Fix Version/s: 4.3.0
• Component/s: action
• Assignee: Harsh J
• Reporter: Harsh J
• Created: 02/Oct/14 03:41
• Updated: 02/Dec/16 21:02
• Resolved: 10/Jan/15 20:10

Description

When you have issues where JT is missing job history or JHS is lacking it, causing JavaActionExecutor to fail when its RunningJob is returned back as null, it prints a very confusing message such as below, that can read instead as "This is not the Job ID I was supposed to find" instead of what is meant to be "I could not find this Job ID on the server":

"JA017: Unknown hadoop job [job_12048563533402_20232] associated with action [1129661-1909061866638236-oozie-oozi-W@java-action]. Failing this action!”

What would instead be clearer is this:

"JA017: Could not lookup launched hadoop job ID [job_12048563533402_20232] which was associated with action [1129661-1909061866638236-oozie-oozi-W@java-action]. Failing this action!”

Patch attached, feel free to refine further during commit if the text is unsatisfactory in parts.

Issue Links

• is related to: OOZIE-2109 Possibly incorrect job ID may be printed for map-reduce action errors