hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HADOOP-4967) Inconsistent state in JVM manager
Date Mon, 19 Jan 2009 18:11:59 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Devaraj Das resolved HADOOP-4967.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 0.21.0
                   0.20.0
                   0.19.1
     Hadoop Flags: [Reviewed]

I just committed this. 

> Inconsistent state in JVM manager
> ---------------------------------
>
>                 Key: HADOOP-4967
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4967
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Devaraj Das
>             Fix For: 0.19.1, 0.20.0, 0.21.0
>
>         Attachments: 4967.patch
>
>
> The following is the scenario:
> -> TT got a LaunchTaskAction. And It found the slot free. It started the TaskRunner
> -> TT received KillJobActtion. It did a runner.kill().
> But, runner.kill() didn't remove JVM Runner from jvmIdToRunner , as it is not polulated
yet. 
> It released the slots.
> -> TaskRunner thread spawned jvm and populated jvmIdToRunner.
> -> The next task getting launched on the slot finds it as busy.

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


Mime
View raw message