[
https://issues.apache.org/jira/browse/MAPREDUCE-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved MAPREDUCE-274.
----------------------------------------
Resolution: Won't Fix
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.
> Hadoop JobClient can return specific exit codes for specific classes of
> exceptions
> ----------------------------------------------------------------------------------
>
> Key: MAPREDUCE-274
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-274
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Hemanth Yamijala
>
> 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 ?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
