[
https://issues.apache.org/jira/browse/HADOOP-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated HADOOP-2570:
----------------------------------
Attachment: HADOOP-2570_1_20080112.patch
bq. 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.
Here is patch which fixes TaskTracker.localizeJob to fix the problem described
above, along with Amareshwari's original fix.
> 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: HADOOP-2570_1_20080112.patch, 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.
