hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-246) Job recovery should fail or kill a job that fails ACL checks upon restart, if the job was running previously
Date Mon, 21 Jul 2014 21:50:40 GMT

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

Allen Wittenauer resolved MAPREDUCE-246.
----------------------------------------

    Resolution: Fixed

I'm going to close this as stale.

> Job recovery should fail or kill a job that fails ACL checks upon restart, if the job
was running previously
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-246
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-246
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>            Reporter: Hemanth Yamijala
>         Attachments: HADOOP-5460-v1.0.patch, HADOOP-5460-v1.0.patch, HADOOP-5460-v1.4.patch,
HADOOP-5460-v1.5.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message