[
https://issues.apache.org/jira/browse/MAPREDUCE-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978091#action_12978091
]
Todd Lipcon commented on MAPREDUCE-2234:
----------------------------------------
test-patch:
[exec]
[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 6 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
(version 1.3.9) warnings.
[exec]
[exec] +1 release audit. The applied patch does not increase the
total number of release audit warnings.
[exec]
[exec] +1 system test framework. The patch passed system test
framework compile.
Unit tests all passed except for the known timeouts.
> If Localizer can't create task log directory, it should fail on the spot
> ------------------------------------------------------------------------
>
> Key: MAPREDUCE-2234
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2234
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: tasktracker
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: mapreduce-2234.txt, mapreduce-2234.txt
>
>
> Currently, it simply emits a warning. Then, when the taskjvm.sh tries to pipe
> its output into this directory, it fails with a strange error code like "exit
> code: 1" which is not intuitive to ops. Instead it should simply throw an
> exception at initialization time rather than attempting to run the task.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
