You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Xuan Gong (JIRA)" <ji...@apache.org> on 2013/05/10 07:59:17 UTC

[jira] [Updated] (MAPREDUCE-4067) Replace YarnRemoteException with IOException in MRv2 APIs

     [ https://issues.apache.org/jira/browse/MAPREDUCE-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xuan Gong updated MAPREDUCE-4067:
---------------------------------

    Attachment: MAPREDUCE-4067.2.patch

1. Change MRClientProtocol API to throw IOException instead of YarnRemoteException
2. In MRClientProtocolPBClientImpl, instead of using RPCUtil.unwrap method to unwrap and throw exceptions, we create new unwrap method to throw IOException.
3. All MR apis will not throw YarnRemoteException anymore, they will wrap YarnRemoteException and throw out IOException instead
                
> 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, MAPREDUCE-4067.2.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