[
https://issues.apache.org/jira/browse/MAPREDUCE-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13035158#comment-13035158
]
Devaraj Das commented on MAPREDUCE-2452:
----------------------------------------
I should ideally put a small sleep between the retries whenever 'offer' returns
false. That would need InterruptedException to be handled. I ideally don't want
to swallow the InterruptedException but if I don't it leads to a big cascading
change in the method declarations in the call hierarchy of the token
cancellation method... I am in two minds on whether to swallow/ignore the
interrupted exception or propagate it all the way up and effect a major change
in the method signatures...
> Delegation token cancellation shouldn't hold global JobTracker lock
> -------------------------------------------------------------------
>
> Key: MAPREDUCE-2452
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2452
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Fix For: 0.23.0
>
> Attachments: cancel-delegation-token-fix.patch
>
>
> Currently, when the JobTracker cancels a job's delegation token (at the end
> of the job), it holds the global lock. This is not desired.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
