[
https://issues.apache.org/jira/browse/MAPREDUCE-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthik Kambatla updated MAPREDUCE-4860:
----------------------------------------
Attachment: mr-4860.patch
Taking a closer look, the problem seems to be with the use of TimerTask/Timer.
If a task is already scheduled, calling task.cancel() from outside the task
doesn't stop the scheduled task, but prevents the task from getting scheduled
another time. However, the task can cancel itself.
The patch:
# adds a check within the task if it has been stopped from outside
# synchronizes changes to delegationTokens
> Inconsistent synchronization in
> mapreduce.security.token.DelegationTokenRenewal
> -------------------------------------------------------------------------------
>
> 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
>
>
> 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