hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4067) Replace YarnRemoteException with IOException in MRv2 APIs
Date Wed, 08 May 2013 19:59:16 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652269#comment-13652269
] 

Vinod Kumar Vavilapalli commented on MAPREDUCE-4067:
----------------------------------------------------

Revisiting this.

I think we are on the correct patch. We should just replace the YarnRemoteException with IOException
in all of MR protocols. Clearly the legacy MR clients don't know or care about YarnRemoteExceptions.
                
> Replace YarnRemoteException with IOException in MRv2 APIs
> ---------------------------------------------------------
>
>                 Key: MAPREDUCE-4067
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4067
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Jitendra Nath Pandey
>            Assignee: Xuan Gong
>            Priority: Critical
>         Attachments: MAPREDUCE-4067.1.patch, MR4067.txt
>
>
> YarnRemoteException is defined as a generic wrapper for all the exceptions in yarn. I
think we should instead throw IOExceptions in the API, which can later be extended for more
specialized exceptions without breaking compatibility.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message