Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-2024

Confusing message when a job can't be looked up by JavaActionExecutor

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 4.0.0
    • Fix Version/s: 4.3.0
    • Component/s: action
    • Labels:
      None

      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.

        Attachments

        1. OOZIE-2024.patch
          1.0 kB
          Harsh J
        2. OOZIE-2024.patch
          1.0 kB
          Harsh J
        3. OOZIE-2024.patch
          1 kB
          Harsh J

          Issue Links

            Activity

              People

              • Assignee:
                qwertymaniac Harsh J
                Reporter:
                qwertymaniac Harsh J
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: