Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <26410282.1197405283148.JavaMail.jira@brutus>
Date: Tue, 11 Dec 2007 12:34:43 -0800 (PST)
From: "Christian Kunz (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-2092) Pipes C++ task does not die even if
 the Java tasks die
In-Reply-To: <1545436.1193130890969.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Christian Kunz commented on HADOOP-2092:
----------------------------------------

We see this a lot: pipes applications continuing as orphan processes after the parent task gets killed (e.g. speculatively executed task killed because of  'Already completed TIP') . When these applications sidestep the mapred framework and communicate to DFS directly using libhdfs, then lthe load to dfs sometimes becomes so high that the job eventually fails. 

> 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
>            Assignee: Amareshwari Sri Ramadasu
>             Fix For: 0.16.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.