Return-Path: Delivered-To: apmail-hbase-user-archive@www.apache.org Received: (qmail 33376 invoked from network); 13 Aug 2010 18:55:03 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 13 Aug 2010 18:55:03 -0000 Received: (qmail 45288 invoked by uid 500); 13 Aug 2010 18:55:02 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 45250 invoked by uid 500); 13 Aug 2010 18:55:01 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 45242 invoked by uid 99); 13 Aug 2010 18:55:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Aug 2010 18:55:01 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jdcryans@gmail.com designates 74.125.82.169 as permitted sender) Received: from [74.125.82.169] (HELO mail-wy0-f169.google.com) (74.125.82.169) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Aug 2010 18:54:55 +0000 Received: by wyg36 with SMTP id 36so3519704wyg.14 for ; Fri, 13 Aug 2010 11:54:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; bh=9rnD0RKGrVI2dtU4yiRi9nyncv9B9uZNsnbTqlHs0MQ=; b=onuM+UoCQNOxJ8Lf6LXfSl8IoHG2f0AAoEGJP482xSKpAVZErkBD6LQTpj9is3ccoN fAa5DqR+HC3KmoaAl2S0GTEh65Ha/YTKs8fzIiq/vKwh0Q/0S2UAVUzkbJp+FlatHxyn W2gGuLLj6/OPsFbDfEFmR+BpGmDrBy7YWb8Wk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=eKB5RCtIb51DmPNLgpJPwZoso0IilRiIbTwB7vQP7Esft2bkq0ZGjmXXZehsK559jJ caf3JhX3A5XPxCCmMpKpETjYjsI3RqB2wHZk53XCvLUNHgZcjSGUy58SYPXp/q5L1usg Sg/SkBP2/UJ3FsSTqx9wjAkXWd5pr1pi45Njs= MIME-Version: 1.0 Received: by 10.216.162.78 with SMTP id x56mr1599086wek.80.1281725673998; Fri, 13 Aug 2010 11:54:33 -0700 (PDT) Sender: jdcryans@gmail.com Received: by 10.216.1.11 with HTTP; Fri, 13 Aug 2010 11:54:33 -0700 (PDT) In-Reply-To: References: Date: Fri, 13 Aug 2010 11:54:33 -0700 X-Google-Sender-Auth: x31CH8QfnAtQoiUOFUDFvo-QWxI Message-ID: Subject: Re: Fw: namenode crash From: Jean-Daniel Cryans To: user@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable u18 should never be used. You say it's crashing on both u17 and u20? How is it crashing? (it's kind of a vague word) Here with use both u14 and u17 on 20 nodes clusters without any issue. J-D On Fri, Aug 13, 2010 at 11:27 AM, Jinsong Hu wrote= : > > > Hi, There: > =A0does anybody know of a good combination of centos version and jdk vers= ion that works stably ? I am using centos version > > Linux =A02.6.18-194.8.1.el5.centos.plus #1 SMP Wed Jul 7 11:45:38 EDT 201= 0 > =A0x86_64 x86_64 x86_64 GNU/Linux > > jdk version > Java(TM) SE Runtime Environment (build 1.6.0_17-b04) > Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01, mixed mode) > > and run the namenode with the following jvm config > -Xmx1000m =A0-XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:+Disable= ExplicitGC -XX:+HeapDumpOnOutOfMemoryError -XX:+UseCompressedOops -XX:+DoEs= capeAnalysis -XX:+AggressiveOpts =A0-Xmx2G > > but it crashed silently after 16 hours. > > I used jdk > Java(TM) SE Runtime Environment (build 1.6.0_20-b02) > Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode) > > with the same jvm config, and the namenode crashed in about 1 week. I sea= rched internet and people say 1.6.0_18 is not good. > but does anybody can recommend a good combination of jdk and os version t= hat can run stably ? > > > This crashing problem doesn't happen with a small cluster of 4 datanodes.= but it happens with a cluster of 17 datanodes. > > Jimmy. > > >