hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Krishna Ramachandran (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1778) CompletedJobStatusStore initialization should fail if {mapred.job.tracker.persist.jobstatus.dir} is unwritable
Date Tue, 08 Jun 2010 12:51:12 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876666#action_12876666

Krishna Ramachandran commented on MAPREDUCE-1778:

If the directory exists and permissions are correct jt can read from or write to - is this
not correct?

Permissions are similar to what is done in JobHistory data

The only other way at least i know is to create a temporary file - something like

   if (!exists) create;

    	Path testpath = new Path(path, "testfile");
    	DataOutputStream out = fs.create(testpath);

Chris is not in favor. If there is a better way let me know. Though this is a one time thing
(when jt starts)

I used hadoop code formatter - will make sure alignments are correct

As for test case, scope of JobStatusPersistency is different  would rather have a separate

> CompletedJobStatusStore initialization should fail if {mapred.job.tracker.persist.jobstatus.dir}
is unwritable
> --------------------------------------------------------------------------------------------------------------
>                 Key: MAPREDUCE-1778
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1778
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobtracker
>            Reporter: Amar Kamat
>            Assignee: Amar Kamat
>         Attachments: mapred-1778-1.patch, mapred-1778-2.patch, mapred-1778.patch
> If {mapred.job.tracker.persist.jobstatus.dir} points to an unwritable location or mkdir
of {mapred.job.tracker.persist.jobstatus.dir} fails, then CompletedJobStatusStore silently
ignores the failure and disables CompletedJobStatusStore. Ideally the JobTracker should bail
out early indicating a misconfiguration.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message