[ https://issues.apache.org/jira/browse/MAPREDUCE-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729789#comment-13729789 ]
Siddharth Seth commented on MAPREDUCE-5384: ------------------------------------------- Isn't it possible for removeDelegationTokenRenewalForJob (during the cancel call) to synchronize on a token which may be stuck in a renewal RPC call ? > Races in DelegationTokenRenewal > ------------------------------- > > Key: MAPREDUCE-5384 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-5384 > Project: Hadoop Map/Reduce > Issue Type: Bug > Affects Versions: 1.2.0, 1.1.2, 1.2.1 > Reporter: Karthik Kambatla > Assignee: Karthik Kambatla > Attachments: mr-5384-0.patch, mr-5384-1.patch > > > There are a couple of races in DelegationTokenRenewal. > One of them was addressed by MAPREDUCE-4860, which introduced a deadlock > while fixing this race. Opening a new JIRA per discussion in MAPREDUCE-5364, > since MAPREDUCE-4860 is already shipped in a release. > Races to fix: > # TimerTask#cancel() disallows future invocations of run(), but doesn't abort > an already scheduled/started run(). > # In the context of DelegationTokenRenewal, RenewalTimerTask#cancel() only > cancels that TimerTask instance. However, it has no effect on any other > TimerTasks created for that token. -- 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