Hadoop Map/Reduce
  1. Hadoop Map/Reduce
  2. MAPREDUCE-274

Hadoop JobClient can return specific exit codes for specific classes of exceptions

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Today if a job tracker becomes unresponsive or dies, the hadoop JobClient throws an exception subclass of IOException and exits with an exit code of 1. However, it would probably fail with the same exit code if there's any other type of exception as well. Programs like HOD which use this client (indirectly through the hadoop script) can make better decisions if the error code is more distinguishable. For e.g. if it's a network related exception, we can treat the cluster are unusable, or retry after awhile etc. More generically, if categories of exceptions can be treated with specific exit codes, it will help.

      Comments ?

        Activity

        Hide
        Allen Wittenauer added a comment -

        I'm closing this as won't fix. Using the exit code like this is fraught with danger. It's much better to exit 1 put throw a message to stderr with the actual problem.

        Show
        Allen Wittenauer added a comment - I'm closing this as won't fix. Using the exit code like this is fraught with danger. It's much better to exit 1 put throw a message to stderr with the actual problem.

          People

          • Assignee:
            Unassigned
            Reporter:
            Hemanth Yamijala
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development