[
https://issues.apache.org/jira/browse/HADOOP-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635888#action_12635888
]
Hadoop QA commented on HADOOP-4232:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12391205/4232-after-review.patch
against trunk revision 700548.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 Eclipse classpath. The patch retains Eclipse classpath integrity.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3405/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3405/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3405/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3405/console
This message is automatically generated.
> Race condition in JVM reuse when more than one slot becomes free
> ----------------------------------------------------------------
>
> Key: HADOOP-4232
> URL: https://issues.apache.org/jira/browse/HADOOP-4232
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.19.0
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Priority: Blocker
> Fix For: 0.19.0
>
> Attachments: 4232-after-review.patch, 4232.patch
>
>
> A race condition exists where there are two or more slots free and there are
> two or more tasks waiting to run. As an example, consider a case where there
> are two free slots and there are two tasks waiting to run. JVM_job1 and
> JVM_job2 are the two idle jvms in memory. A waiting task, task job1_t1, kills
> the JVM_job2 and spawns a new one, JVM_1_job1. While JVM_1_job1 is
> initializing (it is marked busy during initialization), JVM_job1 picks this
> task up and hence this becomes busy as well. Another waiting task, job3_t1
> finds both the JVMs busy and doesn't spawn a new JVM.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
