[
https://issues.apache.org/jira/browse/YARN-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573901#comment-13573901
]
Siddharth Seth commented on YARN-142:
-------------------------------------
bq. and draw attention to the different subclasses in the javadoc if needed.
While YarnRemoteException is a subclass of IOException, explicitly calling it
out in the API isn't super useful. Was hoping to keep exceptions generated by
YARN separate from RPC errors.
The RPC layer, however, doesn not seem to handle anything other than
IOException and it's derivatives. Changing YarnRemoteException to be
independent of IOException would be in incompatible change at a later point -
so maybe we should consider fixing the RPC layer to allow additional exceptions
right now.
> Change YARN APIs to throw IOException
> -------------------------------------
>
> Key: YARN-142
> URL: https://issues.apache.org/jira/browse/YARN-142
> Project: Hadoop YARN
> Issue Type: Sub-task
> Affects Versions: 0.23.3, 2.0.0-alpha
> Reporter: Siddharth Seth
> Assignee: Xuan Gong
> Priority: Critical
> Attachments: YARN-142.1.patch, YARN-142.2.patch, YARN-142.3.patch,
> YARN-142.4.patch
>
>
> Ref: MAPREDUCE-4067
> All YARN APIs currently throw YarnRemoteException.
> 1) This cannot be extended in it's current form.
> 2) The RPC layer can throw IOExceptions. These end up showing up as
> UndeclaredThrowableExceptions.
--
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
