Return-Path: Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: (qmail 25047 invoked from network); 26 Aug 2010 03:00:07 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 26 Aug 2010 03:00:07 -0000 Received: (qmail 81998 invoked by uid 500); 26 Aug 2010 03:00:06 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 81626 invoked by uid 500); 26 Aug 2010 03:00:05 -0000 Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@hadoop.apache.org Delivered-To: mailing list general@hadoop.apache.org Received: (qmail 81618 invoked by uid 99); 26 Aug 2010 03:00:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Aug 2010 03:00:05 +0000 X-ASF-Spam-Status: No, hits=4.4 required=10.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [98.136.44.37] (HELO n61.bullet.mail.sp1.yahoo.com) (98.136.44.37) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 26 Aug 2010 02:59:55 +0000 Received: from [216.252.122.216] by n61.bullet.mail.sp1.yahoo.com with NNFMP; 26 Aug 2010 02:59:35 -0000 Received: from [67.195.9.83] by t1.bullet.sp1.yahoo.com with NNFMP; 26 Aug 2010 02:59:35 -0000 Received: from [98.137.27.128] by t3.bullet.mail.gq1.yahoo.com with NNFMP; 26 Aug 2010 02:59:34 -0000 Received: from [127.0.0.1] by omp202.mail.gq1.yahoo.com with NNFMP; 26 Aug 2010 02:59:34 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 918454.70232.bm@omp202.mail.gq1.yahoo.com Received: (qmail 46932 invoked by uid 60001); 26 Aug 2010 02:59:34 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1282791574; bh=9gr90DBHrdb4z8wKC5dpYR576MeWk3aUHOdXOnKWl/g=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=LVUnd12kuAY5B0hj0lRzW9oFpbMVeC1QPPnbvSY5aQH1c8VRwAWKoMLGvBM+VOMSsRAqiGI8mvdksUclypvaDrEULmCdWhhv5WTrr2WT5WucyCN3rqU+jRTclnQEp7UIT+LOEm8SpcBfPux/yO+ftAP0AvYsQYd0lNebKiwRl5s= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=l37DNp0x7bnsABD+PWkPzOB7TqMMCK27srZdIm8yu0QJDKZHGOTROmr27H0mryQ9qj/3bpYDDbveSg2HoHM52CnkFCuMD+85mDqXKC/nM5nDZMTZfWRGyVk1QL+RogdpW/cChOoxAXKRgvE0M93vnf37yiJU7foif1flGJZQ/m8=; Message-ID: <698249.46749.qm@web114510.mail.gq1.yahoo.com> X-YMail-OSG: 43iyqEsVM1kRrmUktws.cMt68Shi9M87nNTBtR.IZ8PFMLC xsY1dBxrm8fTsNXB65T9wj7AJjve19dANalcU18NHWadzoSOgpDwROWIfgS7 OZA86gozLQEwdH5YKDq8bk6BNodTAOBvejPOwzeLPSP.P7nwN9uj3rCEM0fU dsx.Dn7u5aVmaaL20AEf9fXxitEz7h1Q7HJmLSeNT1oWCyO1a45BoEyf0Qf. tGf8Xh0ot0pZN3N.GfUWosnQBi14RRbKLtUPE.U2GAb_s4VuSmACqWkYV.W4 Ed8wo8D1RlIZ0ODFdsx1O6NqS4ETaF6oMtbyZLN26pzZ43iyG1bI2tJKz.yn TryAt0w-- Received: from [67.180.86.237] by web114510.mail.gq1.yahoo.com via HTTP; Wed, 25 Aug 2010 19:59:34 PDT X-Mailer: YahooMailRC/470 YahooMailWebService/0.8.105.279950 References: <715590.78832.qm@web114505.mail.gq1.yahoo.com> <194169.50990.qm@web114512.mail.gq1.yahoo.com> Date: Wed, 25 Aug 2010 19:59:34 -0700 (PDT) From: C J Subject: Re: Child processes on datanodes/task trackers To: general@hadoop.apache.org In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-793388696-1282791574=:46749" --0-793388696-1282791574=:46749 Content-Type: text/plain; charset=us-ascii Thanks Ted! I did a jstack and it seems there is an issue with ehcache that I am using in the mapper task. "net.sf.ehcache.CacheManager@57ac3379" daemon prio=10 tid=0x0000000059180800 nid=0x379e in Object.wait() [0x0000000041506000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x00002aaabb0b89a8> (a java.util.TaskQueue) at java.util.TimerThread.mainLoop(Timer.java:509) - locked <0x00002aaabb0b89a8> (a java.util.TaskQueue) at java.util.TimerThread.run(Timer.java:462) Locked ownable synchronizers: - None . . . The hadoop version I am using is 0.20.2. Thanks. ________________________________ From: Ted Yu To: general@hadoop.apache.org Sent: Wed, August 25, 2010 7:34:35 PM Subject: Re: Child processes on datanodes/task trackers After you obtain pid, you can use jstack to see what the Child process was doing. What hadoop version are you using ? On Wed, Aug 25, 2010 at 7:28 PM, C J wrote: > Thanks for your reply. > > Some of these child tasks belong to successful jobs. I am wondering why > they are > still hanging there for long finished jobs. > > > > > > ________________________________ > From: Ted Yu > To: general@hadoop.apache.org > Sent: Wed, August 25, 2010 4:17:38 PM > Subject: Re: Child processes on datanodes/task trackers > > Use jps to find out pid of the Child. > Then use this to find out which job the Child belongs to: > ps aux | grep > > On Wed, Aug 25, 2010 at 12:20 PM, C J wrote: > > > Hi, > > > > I wanted to know why I see running Child processes on my datanodes even > > though > > there is no job running at that time. Are these left over from failed > > attempts? > > > > Is there anything I can do to keep these clean? > > > > Thanks, > > Deepika > > > > > > > > > > > --0-793388696-1282791574=:46749--