Return-Path: Delivered-To: apmail-hadoop-core-user-archive@www.apache.org Received: (qmail 87445 invoked from network); 9 Feb 2009 06:04:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Feb 2009 06:04:28 -0000 Received: (qmail 25796 invoked by uid 500); 9 Feb 2009 06:04:22 -0000 Delivered-To: apmail-hadoop-core-user-archive@hadoop.apache.org Received: (qmail 25740 invoked by uid 500); 9 Feb 2009 06:04:22 -0000 Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-user@hadoop.apache.org Delivered-To: mailing list core-user@hadoop.apache.org Received: (qmail 25729 invoked by uid 99); 9 Feb 2009 06:04:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 Feb 2009 22:04:22 -0800 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mry.maillist@gmail.com designates 209.85.146.179 as permitted sender) Received: from [209.85.146.179] (HELO wa-out-1112.google.com) (209.85.146.179) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Feb 2009 06:04:12 +0000 Received: by wa-out-1112.google.com with SMTP id v27so936581wah.29 for ; Sun, 08 Feb 2009 22:03:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=+NvrUgGaN9niTq45ltwQ76PpB6PzffdCjJldCaeKJ/U=; b=c/lCAtPJWkFwazhYsxRVriQ4M/9RMhEC4wB3qd2Fof3E9D+QX4RpLAu/WsrGasau98 s1UZpVcXHijXyVtO2h922ybvYhwx259HZ1YFqvOb5DMhXVOF9cTov2u6RoPrErlpX3IT Jo1z74Dxok9faSVquRciOu8rKEyOqXKHkaWdU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=KDAn5uego3uaIZ3undkCoFdLoMnQiFcNF9NpvTH0V6sEyPShiJQ7TsmO6VqVUCissR 2Fpg9zLPilmNdKppaQuQ72WOvJam8K+j6C2KXqoSJmxmLzq8n074IfzX7u8APvOIec9j iDbw+ID835SxyNdo9Ww+teBX/aQCBIdgpZ5tI= MIME-Version: 1.0 Received: by 10.114.159.17 with SMTP id h17mr3305232wae.124.1234159431424; Sun, 08 Feb 2009 22:03:51 -0800 (PST) In-Reply-To: References: Date: Mon, 9 Feb 2009 14:03:51 +0800 Message-ID: Subject: Re: After hadoop jobtracker runs for a long time, jobtracker may comsume 100% cpu (one cpu core is fully consume), why? From: Ruyue Ma To: core-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=00163645883e819b6c04627622f3 X-Virus-Checked: Checked by ClamAV on apache.org --00163645883e819b6c04627622f3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Our hadoop version is checked out from truck version at 2008.10.22. When this problem appeared, our cluster didn't have any job running. The cluster was idle! On Mon, Feb 9, 2009 at 1:56 PM, Ruyue Ma wrote: > Hi, Everyone > > After hadoop jobtracker runs for a long time, jobtracker may comsume 100% > cpu (one cpu core is fully consume). > > We have encountered this problem sever times. When it happens, it is hardly > to submit job to jobtracker and visit the jobtracker web page. > > Anybody encounter this? > > is there an existed patch to fix it? > > Thanks > Ruyue Ma > Baidu.com > --00163645883e819b6c04627622f3--