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

zhihai xu commented on YARN-2893:
---------------------------------

Hi [~jira.shegalov], It looks like the Credentials from client is not used by 
YARN in non-secure mode. Can we set the Tokens to null in non-secure mode? if 
we don't want to parseCredentials(reject an application with corrupted 
credentials) in non-secure mode.
{code}
submissionContext.getAMContainerSpec().setTokens(null);
{code}

For me, it is reasonable to check Credentials parameter in non-secure mode, 
because any parameter from Client should be valid and it is the Client's 
responsibility to maintain these parameters and Client can set the Tokens to 
null if Client doesn't want to pass any tokens to RM.

> AMLaucher: sporadic job failures due to EOFException in readTokenStorageStream
> ------------------------------------------------------------------------------
>
>                 Key: YARN-2893
>                 URL: https://issues.apache.org/jira/browse/YARN-2893
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.4.0
>            Reporter: Gera Shegalov
>            Assignee: zhihai xu
>         Attachments: YARN-2893.000.patch, YARN-2893.001.patch, 
> YARN-2893.002.patch
>
>
> MapReduce jobs on our clusters experience sporadic failures due to corrupt 
> tokens in the AM launch context.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to