hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-737) Some Exceptions no longer need to be wrapped by YarnException and can be directly thrown out after YARN-142
Date Fri, 07 Jun 2013 00:56:20 GMT

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

Bikas Saha commented on YARN-737:
---------------------------------

Redundant code in the first line?
{code}
+      tokenId = newContainerTokenIdentifier(containerToken);
+      tokenId = new ContainerTokenIdentifier();
{code}

We probably do want to continue to wrap IOExceptions, as on the client side the semantics
are that IOException comes from RPC and not from the server. We should ideally create context
specific exceptions to replace the wrapped IOExceptions later on in a different jira.
                
> Some Exceptions no longer need to be wrapped by YarnException and can be directly thrown
out after YARN-142 
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-737
>                 URL: https://issues.apache.org/jira/browse/YARN-737
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Jian He
>            Assignee: Jian He
>         Attachments: YARN-737.1.patch, YARN-737.2.patch, YARN-737.3.patch
>
>


--
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