hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Created] (YARN-1146) RM DTSM and RMStateStore mismanage sequence number
Date Wed, 04 Sep 2013 17:16:53 GMT
Daryn Sharp created YARN-1146:

             Summary: RM DTSM and RMStateStore mismanage sequence number
                 Key: YARN-1146
                 URL: https://issues.apache.org/jira/browse/YARN-1146
             Project: Hadoop YARN
          Issue Type: Bug
    Affects Versions: 2.0.0-alpha
            Reporter: Daryn Sharp

{{RMDelegationTokenSecretManager}} implements {{storeNewToken}} and {{updateStoredToken}}
(renew) to pass the token and its sequence number to {{RMStateStore#storeRMDelegationTokenAndSequenceNumber}}.

There are two problems:
# The assumption is that new tokens will be synchronously stored in-order.  With an async
secret manager this may not hold true and the state's sequence number may be incorrect.
# A token renewal will reset the state's sequence number to _that token's_ sequence number.

Bug #2 is generally masked.  Creating a new token (with the first caveat) will bump the state's
sequence number back up.  Restoring the dtsm will first set the state's stored sequence number,
then re-add all the tokens which will update the sequence number if the token's sequence number
is greater than the dtsm's current sequence number.

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

View raw message