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 D5092100FC for ; Tue, 11 Jun 2013 00:49:10 +0000 (UTC) Received: (qmail 29975 invoked by uid 500); 11 Jun 2013 00:49:08 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 29924 invoked by uid 500); 11 Jun 2013 00:49:08 -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 29916 invoked by uid 99); 11 Jun 2013 00:49:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Jun 2013 00:49:08 +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: domain of ramkrishna.s.vasudevan@gmail.com designates 209.85.216.45 as permitted sender) Received: from [209.85.216.45] (HELO mail-qa0-f45.google.com) (209.85.216.45) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Jun 2013 00:49:03 +0000 Received: by mail-qa0-f45.google.com with SMTP id ci6so2635174qab.18 for ; Mon, 10 Jun 2013 17:48:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=43lltlUvny/77LnTglXGBJI14yYqh/CnaqOG3Y5DMv0=; b=Bfa2OrGTSce2DClxFf4gsctnb0szYHG4ezFuJDM1PFwr4UhQo6USF8hy0L4TJijBP+ 9SV3wjQDVqYkT695OBsWLMj0vwE2YXQgsJXV0nWSOc2nHyRWhxOPrDdU/ZQZ8WAd4x79 1z2323LAwzS7zuefq8dsHdG4o8+0s3WhkigQD/kwBzx69x7UGtqnPmSvac2/drj+FkC3 BL55OegBwbEudzBX9ftg9OYChaOPMoalmMILdYzhDIE5sp5lxNaSlMn618pqaGD3wEiP xNZ8rKk0h0d+friMdD3x6zf1aZ7MlOdBQl5mBiALT2riX7QB6vk0Rpn5Uo80ESLU5ZLU Xt/g== MIME-Version: 1.0 X-Received: by 10.229.195.71 with SMTP id eb7mr4767170qcb.45.1370911722649; Mon, 10 Jun 2013 17:48:42 -0700 (PDT) Received: by 10.49.116.143 with HTTP; Mon, 10 Jun 2013 17:48:42 -0700 (PDT) In-Reply-To: References: Date: Tue, 11 Jun 2013 06:18:42 +0530 Message-ID: Subject: Re: SSD vs Spinning disks From: ramkrishna vasudevan To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=001a11c305d03f3c5804ded6424f X-Virus-Checked: Checked by ClamAV on apache.org --001a11c305d03f3c5804ded6424f Content-Type: text/plain; charset=ISO-8859-1 Currently this feature is not available. But there is a JIRA that has been raised to help in achieving this. https://issues.apache.org/jira/browse/HBASE-6572. Feel free to give your comments over there. Regards Ram On Tue, Jun 11, 2013 at 6:14 AM, Lucas Stanley wrote: > Hi, > > If I understand HBase's architecture correctly, it is only the WAL that > needs to be placed on a SSD to make writes perform better? > > Because a write comes to a region server, then goes to the WAL and > memstore. If the WAL is on SSD on this node and 2 other DataNodes, then the > append writes will finish much faster, right? > > So, is there a way in HDFS to tell it to only put the HBase WALs > (/hbase/.logs/) on a SSD disk and to keep the other HFiles on traditional > spinning disks? > --001a11c305d03f3c5804ded6424f--