[
https://issues.apache.org/jira/browse/YARN-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647272#comment-13647272
]
Vinod Kumar Vavilapalli commented on YARN-629:
----------------------------------------------
bq. YarnRemoteException is not rooted as IOException now. For ugi.doAs(), it
throws IOException, InterruptedException, UndeclaredThrowableException,etc, but
does not throw YarnRemoteException. So, we can not Explicitly catch
YarnRemoteException.
Then why was this code catching YarnRemoteException *before* your patch ? Try
changing client.ping() to throw YarnRemoteException, like we do in real
protocols.
bq. I think if YarnRemoteException is throw inside the doAs(), it will be
wrapped. So by calling getCause() will get it back.
Why didn't we need this before and only now?
bq. Should it be YarnRemoteException ???
No, see NMNotYetReadyException and InvalidContainerException.
> Make YarnRemoteException not be rooted at IOException
> -----------------------------------------------------
>
> Key: YARN-629
> URL: https://issues.apache.org/jira/browse/YARN-629
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Xuan Gong
> Assignee: Xuan Gong
> Attachments: YARN-629.1.patch, YARN-629.2.patch
>
>
> After HADOOP-9343, it should be possible for YarnException to not be rooted
> at IOException
--
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
