[
https://issues.apache.org/jira/browse/HADOOP-5460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681164#action_12681164
]
Nigel Daley commented on HADOOP-5460:
-------------------------------------
Clearly there are a number of important test cases here that need consideration:
Upon JT restart, these changes are made to ACLs and queues:
1) user removed from all queues where her jobs are running
2) user removed from one queue where her jobs are running
3) user moved to a different queue
4) queue renamed
5) queue removed
6) queue maxRunningJobs is smaller than number of currently running jobs
...
> Job recovery should fail or kill a job that fails ACL checks upon restart, if
> the job was running previously
> ------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-5460
> URL: https://issues.apache.org/jira/browse/HADOOP-5460
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Reporter: Hemanth Yamijala
>
> Consider a scenario where a job was submitted to the M/R system and runs for
> a while. Then say the JT is restarted, and before that the ACLs for the user
> are changed so that that user can no longer submit jobs to that queue. Since
> the job could potentially be using resources alloted to that queue and could
> be account for it, this might lead to accounting inconsistencies. A
> suggestion is for the jobtracker to fail / kill this job.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
