You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Karthik Kambatla (JIRA)" <ji...@apache.org> on 2012/12/13 01:49:21 UTC

[jira] [Updated] (MAPREDUCE-4860) DelegationTokenRenewal attempts to renew token even after a job is removed

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

Karthik Kambatla updated MAPREDUCE-4860:
----------------------------------------

    Summary: DelegationTokenRenewal attempts to renew token even after a job is removed  (was: Inconsistent synchronization in mapreduce.security.token.DelegationTokenRenewal)
    
> DelegationTokenRenewal attempts to renew token even after a job is removed
> --------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4860
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4860
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 1.1.1
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>         Attachments: mr-4860.patch, mr-4860.patch, mr-4860.patch, mr-4860.patch
>
>
> mapreduce.security.token.DelegationTokenRenewal synchronizes on removeDelegationToken, but fails to synchronize on addToken, and renewing tokens in run().
> This inconsistency is exposed by frequent failures of TestDelegationTokenRenewal:
> {noformat}
> Error Message
> renew wasn't called as many times as expected expected:<4> but was:<5>
> Stacktrace
> junit.framework.AssertionFailedError: renew wasn't called as many times as expected expected:<4> but was:<5>
> 	at org.apache.hadoop.mapreduce.security.token.TestDelegationTokenRenewal.testDTRenewal(TestDelegationTokenRenewal.java:317)
> 	at org.apache.hadoop.mapreduce.security.token.TestDelegationTokenRenewal.testDTRenewalAfterClose(TestDelegationTokenRenewal.java:338)
> {noformat}

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