Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 78AFCE600 for ; Fri, 8 Feb 2013 01:44:11 +0000 (UTC) Received: (qmail 95217 invoked by uid 500); 8 Feb 2013 01:44:09 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 95175 invoked by uid 500); 8 Feb 2013 01:44:09 -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 95166 invoked by uid 99); 8 Feb 2013 01:44:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Feb 2013 01:44:09 +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 (nike.apache.org: domain of kevin.odell@cloudera.com designates 209.85.215.44 as permitted sender) Received: from [209.85.215.44] (HELO mail-la0-f44.google.com) (209.85.215.44) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Feb 2013 01:44:02 +0000 Received: by mail-la0-f44.google.com with SMTP id eb20so3309248lab.17 for ; Thu, 07 Feb 2013 17:43:42 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=bJVYTxSdyO7yTBfs/yoXBbQ8cO9qp9AFZRXFW6lrEe8=; b=ANfKTP4vo7Qg1O2mBsS2Vty2mPnx20NiVtTdngdl3NaIIZdsYi1BgUJQM7S1Z2Q750 wuDCooUm3JDr20zJ8bVC5HLo6AViJx78xy6dTljV/yaJiNjJab8mMQAIlOoM4K5ClJft bPATdw38S/2Lja+2iDy2FjJq2rmcWG2D32x6KHouEyTZkrmZNeJcBzFHB02Zv7M3M9yA SanIHtTX9ADH+6pwC23ACaeJdiugyxp7P2Its6DPkTWNPMVUHWqx1UGTLAIxZJEpjPjv iXakCj6+cKDE7Ou6uUX7akDr9DG379OPrgrfxrXo2OgiY3FoObn8QPHcDD0hJjyIGYW4 AOXQ== MIME-Version: 1.0 X-Received: by 10.152.147.36 with SMTP id th4mr3268152lab.19.1360287821896; Thu, 07 Feb 2013 17:43:41 -0800 (PST) Received: by 10.112.16.227 with HTTP; Thu, 7 Feb 2013 17:43:41 -0800 (PST) In-Reply-To: References: Date: Thu, 7 Feb 2013 20:43:41 -0500 Message-ID: Subject: Re: Acceptable CPU_WIO % ? From: "Kevin O'dell" To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=e89a8f22c3816a9b0604d52cb074 X-Gm-Message-State: ALoCoQlvmZGjRtYUYfHksc9x12XVEpTy354szqrKahWc3lDn8+03YlMtB+a9P5k/MhDBl7rT4r5L X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f22c3816a9b0604d52cb074 Content-Type: text/plain; charset=ISO-8859-1 Hey JM, Why RAID0? That has a lot of disadvantages to using a JBOD configuration? Wait I/O is a symptom, not a problem. Are you actually experiencing a problem or are you treating for something you think should be lower? On Thu, Feb 7, 2013 at 8:19 PM, Jean-Marc Spaggiari wrote: > Hi, > > What is an acceptable CPU_WIO % while running an heavy MR job? Should > we also try to keep that under 10%? Or it's not realistic and we will > see more about 50%? > > One of my nodes is showing 70% :( It's WAY to much. I will add another > disk tomorrow and put them in RAID0, but I'm wondering how low shoud I > go? > > JM > -- Kevin O'Dell Customer Operations Engineer, Cloudera --e89a8f22c3816a9b0604d52cb074--