hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Omkar Vinit Joshi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-693) Sending NMToken to AM on allocate call
Date Thu, 13 Jun 2013 01:59:20 GMT

     [ https://issues.apache.org/jira/browse/YARN-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Omkar Vinit Joshi updated YARN-693:
-----------------------------------

    Description: 
This is part of YARN-613.
As per the updated design, AM will receive per NM, NMToken in following scenarios
* AM is receiving first container on underlying NM.
* AM is receiving container on underlying NM after either NM or RM rebooted.
** After RM reboot, as RM doesn't remember (persist) the information about keys issued per
AM per NM, it will reissue tokens in case AM gets new container on underlying NM. However
on NM side NM will still retain older token until it receives new token to support long running
jobs (in work preserving environment).
** After NM reboot, RM will delete the token information corresponding to that AM for all
AMs.
* AM is receiving container on underlying NM after NMToken master key is rolled over on RM
side.
In all the cases if AM receives new NMToken then it is suppose to store it for future NM communication
until it receives a new one.

  was:
This is part of YARN-613.
As per the updated design, AM will receive per NM, NMToken in following scenarios
* AM is receiving first container on underlying NM.
* AM is receiving container on underlying NM after either NM or RM rebooted.
** After RM reboot, as RM doesn't remember (persist) the information about keys issued per
AM per NM, it will reissue tokens in case AM gets new container on underlying NM. However
on NM side NM will still retain older token until it receives new token to support long running
jobs (in work preserving environment).
** After NM reboot, RM will delete the token information corresponding to all AMs.
* AM is receiving container on underlying NM after NMToken master key is rolled over on RM
side.
In all the cases if AM receives new NMToken then it is suppose to store it for future NM communication
until it receives a new one.

    
> Sending NMToken to AM on allocate call
> --------------------------------------
>
>                 Key: YARN-693
>                 URL: https://issues.apache.org/jira/browse/YARN-693
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Omkar Vinit Joshi
>            Assignee: Omkar Vinit Joshi
>
> This is part of YARN-613.
> As per the updated design, AM will receive per NM, NMToken in following scenarios
> * AM is receiving first container on underlying NM.
> * AM is receiving container on underlying NM after either NM or RM rebooted.
> ** After RM reboot, as RM doesn't remember (persist) the information about keys issued
per AM per NM, it will reissue tokens in case AM gets new container on underlying NM. However
on NM side NM will still retain older token until it receives new token to support long running
jobs (in work preserving environment).
> ** After NM reboot, RM will delete the token information corresponding to that AM for
all AMs.
> * AM is receiving container on underlying NM after NMToken master key is rolled over
on RM side.
> In all the cases if AM receives new NMToken then it is suppose to store it for future
NM communication until it receives a new one.

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