[
https://issues.apache.org/jira/browse/MAPREDUCE-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242773#comment-13242773
]
Siddharth Seth commented on MAPREDUCE-4067:
-------------------------------------------
YarnRemoteException was serializing the actual exception and sending it over
the wire. It was missing an unwind method to get the actual exception. IAC -
clients should not be expected to unwind and that should've been handled in the
RPC layer itself.
Instead of having the APIs throw an IOException, I'd prefer to define a Yarn /
HadoopException which extends Exception and can later be sub-classed for more
specific exceptions. Also, possibly add error codes to these exceptions as well
as to what is sent over the wire. That may make things easier for clients
written in other languages.
> 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: Siddharth Seth
> Priority: Blocker
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
