hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5460) Job recovery should fail or kill a job that fails ACL checks upon restart, if the job was running previously
Date Wed, 06 May 2009 04:42:30 GMT

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

Amar Kamat updated HADOOP-5460:
-------------------------------

    Attachment: HADOOP-5460-v1.4.patch

Attaching a new patch that fixes a bug in the previous patch. Result of test-patch
{code}
[exec] +1 overall.  
     [exec] 
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec] 
     [exec]     +1 tests included.  The patch appears to include 3 new or modified tests.
     [exec] 
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning messages.
     [exec] 
     [exec]     +1 javac.  The applied patch does not increase the total number of javac compiler
warnings.
     [exec] 
     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs warnings.
     [exec] 
     [exec]     +1 Eclipse classpath. The patch retains Eclipse classpath integrity.
     [exec] 
     [exec]     +1 release audit.  The applied patch does not increase the total number of
release audit warnings.
{code}
Running ant test now.

> 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
>         Attachments: HADOOP-5460-v1.0.patch, HADOOP-5460-v1.0.patch, HADOOP-5460-v1.4.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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message