You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Devaraj Das (JIRA)" <ji...@apache.org> on 2007/10/23 12:48:50 UTC

[jira] Updated: (HADOOP-2092) Pipes C++ task does not die even if the Java tasks die

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

Devaraj Das updated HADOOP-2092:
--------------------------------

    Fix Version/s:     (was: 0.16.0)
                   0.15.0
         Priority: Blocker  (was: Major)
      Description: 
Pipes process does not die, when the java map task  dies.
Pipes process does not die even when the cluster is down.

  was:

Pipes process does not die, when the java map task  dies.
Pipes process does not die even when the cluster is down.


Noticed an instance of this bug on an app whose pipes process ran for two complete hours after the parent java map task died.
I think we should introduce a ping mechanism, similar to the one we have for the task -> tasktracker communication, that periodically pings to check whether the java map/reduce process is up.

> Pipes C++ task does not die even if the Java tasks die
> ------------------------------------------------------
>
>                 Key: HADOOP-2092
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2092
>             Project: Hadoop
>          Issue Type: Bug
>          Components: pipes
>            Reporter: Amareshwari Sri Ramadasu
>            Priority: Blocker
>             Fix For: 0.15.0
>
>
> Pipes process does not die, when the java map task  dies.
> Pipes process does not die even when the cluster is down.

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