[
https://issues.apache.org/jira/browse/HADOOP-5471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amareshwari Sriramadasu updated HADOOP-5471:
--------------------------------------------
Status: Patch Available (was: Open)
test-patch result:
{noformat}
[exec]
[exec] -1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] -1 tests included. The patch doesn't appear to include any new
or modified tests.
[exec] Please justify why no tests are needed for
this patch.
[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.
[exec]
{noformat}
It is difficult to write testcase for this.
> SyncLogs thread in Child.java would update wrong file for a cleanup attempt,
> in some cases.
> -------------------------------------------------------------------------------------------
>
> Key: HADOOP-5471
> URL: https://issues.apache.org/jira/browse/HADOOP-5471
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.19.1
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Fix For: 0.19.2
>
> Attachments: patch-5471.txt
>
>
> This happens in the following scenario:
> If jvm is launched for a cleanup attempt and getTask has not returned yet.
> thus, isCleanup value is not obtained yet. But, the SyncLogs thread would do
> a syncLogs with wrong isCleanup value (i.e. with wrong index file).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
