You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Omkar Vinit Joshi (JIRA)" <ji...@apache.org> on 2013/05/31 02:22:20 UTC

[jira] [Commented] (YARN-692) Creating AMNMToken master key on RM and sharing it with NM as a part of RM-NM heartbeat.

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

Omkar Vinit Joshi commented on YARN-692:
----------------------------------------

As a part of this patch only enabling following features.
* During start RM generates NMTokenMasterKey
* For Every NodeManager registration master key is shared along with containerTokenMasterKey
* If there is a rollover then in the hearbeat master key will be shared.

RM at present doesn't send NMToken at container allocation (will be there in YARN-693).
AM at present doesn't store NMToken ...(will be there in YARN-693)
AM at present doesn't send these tokens to NM for all AM-NM communication (will be there in YARN-694).
NM at present doesn't verify the NMToken (will be there in YARN-694).

Added test cases to verify RMNMSecretKeys - at rm start and at roll over.
                
> Creating AMNMToken master key on RM and sharing it with NM as a part of RM-NM heartbeat.
> ----------------------------------------------------------------------------------------
>
>                 Key: YARN-692
>                 URL: https://issues.apache.org/jira/browse/YARN-692
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Omkar Vinit Joshi
>            Assignee: Omkar Vinit Joshi
>
> This is related to YARN-613 . Here we will be implementing AMNMToken generation on RM side and sharing it with NM during RM-NM heartbeat. As a part of this JIRA mater key will only be made available to NM but there will be no validation done until AM-NM communication is fixed.

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