hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2570) streaming jobs fail after HADOOP-2227
Date Fri, 11 Jan 2008 21:30:34 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558133#action_12558133

Arun C Murthy commented on HADOOP-2570:

Please ignore my previous comments... it's been a long day (maybe the following ones too!

It seems like the test cases don't have a jar and hence there is an 'if' check in TaskTracker.localizeJob
which fails and hence the "work" directory isn't created. This explains the exception seen
in the TaskTracker.launchTaskForJob function. 

I didn't make any headway after that...

> streaming jobs fail after HADOOP-2227
> -------------------------------------
>                 Key: HADOOP-2570
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2570
>             Project: Hadoop
>          Issue Type: Bug
>          Components: contrib/streaming
>    Affects Versions: 0.15.2
>            Reporter: lohit vijayarenu
>            Assignee: Amareshwari Sri Ramadasu
>            Priority: Blocker
>             Fix For: 0.15.3
>         Attachments: patch-2570.txt
> HADOOP-2227 changes jobCacheDir. In streaming, jobCacheDir was constructed like this
> {code}
> File jobCacheDir = new File(currentDir.getParentFile().getParent(), "work");
> {code}
> We should change this to get it working. Referring to the changes made in HADOOP-2227,
I see that the APIs used in there to construct the path are not public. And hard coding the
path in streaming does not look good. thought?

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

View raw message