Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 790F810A7E for ; Tue, 3 Jun 2014 16:35:10 +0000 (UTC) Received: (qmail 45215 invoked by uid 500); 3 Jun 2014 16:35:04 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 45039 invoked by uid 500); 3 Jun 2014 16:35:04 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 44969 invoked by uid 99); 3 Jun 2014 16:35:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jun 2014 16:35:04 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [209.85.216.49] (HELO mail-qa0-f49.google.com) (209.85.216.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jun 2014 16:34:57 +0000 Received: by mail-qa0-f49.google.com with SMTP id cm18so5086215qab.36 for ; Tue, 03 Jun 2014 09:34:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=Z8eyMH7f8+PSBS/IGgtEi2NntIYRsCfUuRu0FbfiHqE=; b=ilL5HOGXjOYv6z65pIANpKKk5Xg8Wg+8HMvd6+MHgIOR+zhwvSJMssed0NWEe2wGMH TtSHjGokxWrRlEHM41zKMZpi/z3TNUvHbfeC9HTdwr7j8/JSznqQjbV2h9udvUuXFxsL SAIAe+k44dsk0bbtOhaofPBolGwzYPGOrbNn0Hsylt3fK9cb0kd8cf1QB1RJUMGJIKyE 0QWV4t/LXaa//JMsr+ydXpzmhhVsTpnmBVdkE6rZkALRnXze3T+hUZeFcFXdMZ6bn+g3 c1tLLmi4GOlctm0gOPGm8KYtIoFF297gAX8UTgDKn1B3EXQgSNyb25Z7mmyX3fS6RQyV P4IA== X-Gm-Message-State: ALoCoQmK9CY2aMyWTB6xX1pFGvb8PZpTjW7xW5Ba0a47K+39el6o4U0sRqRpgB3aDzywOVhxLpXE MIME-Version: 1.0 X-Received: by 10.224.104.5 with SMTP id m5mr54516882qao.9.1401813276883; Tue, 03 Jun 2014 09:34:36 -0700 (PDT) Received: by 10.229.5.4 with HTTP; Tue, 3 Jun 2014 09:34:36 -0700 (PDT) X-Originating-IP: [96.45.202.246] Date: Tue, 3 Jun 2014 12:34:36 -0400 Message-ID: Subject: 100% CPU utilization on idle HDFS Data Nodes From: Shayan Pooya To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001a1132f4886910c304faf116c5 X-Virus-Checked: Checked by ClamAV on apache.org --001a1132f4886910c304faf116c5 Content-Type: text/plain; charset=UTF-8 I have a three node HDFS cluster with a name-node. There is absolutely no IO going on this cluster or any jobs running on it and I just use it for testing the Disco HDFS integration. I noticed that two of the three data-nodes are using 100% CPU. They have been running for a long time (2 months) but with no jobs running on them and almost no usage: $ hadoop version Hadoop 2.3.0 Subversion http://svn.apache.org/repos/asf/hadoop/common -r 1567123 Compiled by jenkins on 2014-02-11T13:40Z Compiled with protoc 2.5.0 >From source with checksum dfe46336fbc6a044bc124392ec06b85 Is this a known bug? --001a1132f4886910c304faf116c5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I have a three node HDFS cluster with a nam= e-node.=C2=A0 There is absolutely no IO going on this cluster or any jobs r= unning on it and I just use it for testing the Disco HDFS integration.
<= /div> I noticed that two of the three data-nodes are using 100% CPU.=C2=A0 They h= ave been running for a long time (2 months) but with no jobs running on the= m and almost no usage:

$ hadoop version
Hadoop 2.3.0
Sub= version http://sv= n.apache.org/repos/asf/hadoop/common -r 1567123
Compiled by jenkins on 2014-02-11T13:40Z
Compiled with protoc 2.5.0
F= rom source with checksum dfe46336fbc6a044bc124392ec06b85

= Is this a known bug?

--001a1132f4886910c304faf116c5--