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 BAA0B73FB for ; Tue, 29 Nov 2011 07:37:39 +0000 (UTC) Received: (qmail 774 invoked by uid 500); 29 Nov 2011 07:37:38 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 99720 invoked by uid 500); 29 Nov 2011 07:37:37 -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 99709 invoked by uid 99); 29 Nov 2011 07:37:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Nov 2011 07:37:34 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of yaojingguo@gmail.com designates 74.125.83.41 as permitted sender) Received: from [74.125.83.41] (HELO mail-ee0-f41.google.com) (74.125.83.41) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Nov 2011 07:37:28 +0000 Received: by eekc14 with SMTP id c14so137635eek.14 for ; Mon, 28 Nov 2011 23:37:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=JL8oK6mofLZn2A/QJXHzpauFEpqnQ/x9LSCUSt2EpKY=; b=B1xjW6/7mOGaP1pLj5LrLBu7YVQxFbW4VrQJ5xPNVeaTMikhtHeMv0oHup4hzu45z+ xl0RSuI3KXEZWlwhfPz1hmSL8Q1ijj6IMTRN2PxG0mhZFJCt5mif/tSZ0Ce5yN/09XFQ 9A6MU00KQR9YUKkcWESGRjK3B+Bb9hzBAZqWQ= MIME-Version: 1.0 Received: by 10.227.205.14 with SMTP id fo14mr10428060wbb.22.1322552226804; Mon, 28 Nov 2011 23:37:06 -0800 (PST) Received: by 10.216.71.197 with HTTP; Mon, 28 Nov 2011 23:37:06 -0800 (PST) Date: Tue, 29 Nov 2011 15:37:06 +0800 Message-ID: Subject: Use single cluster or two clusters for log analysis and HBase? From: jingguo yao To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=00151749f35cacf52604b2daaf0a --00151749f35cacf52604b2daaf0a Content-Type: text/plain; charset=ISO-8859-1 I want to set up Hadoop clusters. There are two workloads. One is log analysis which is using MapReduce to process big log files in HDFS. The other is HBase which is used to serve random table queries. I have two choices to set up my Hadoop clusters. One is to use one Hadoop cluster. Log analysis and HBase use the same cluster. Its advantages are: 1 There is only one Hadoop cluster which I need to manage. 2 Both MapReduce and HBase can use this big cluster which has more storage and more powerful computation capability. Its disadvantages: 1 Running MapReduce jobs may slow down the random HBase table queries. The other choice is to use two clusters. Cluster A is for log analysis. Cluster B is for HBase. Its advantages are: 1 There are no interferences between log analysis and HBase table queries. Its disadvantages: 1. There are two Hadoop clusters which need to be managed. 2. Both log analysis and HBase queries can only use a small Hadoop cluster which has less storage and less powerful computation capability. I don't know which choice is better. Can anybody give me some advice on this? Thanks. -- Jingguo --00151749f35cacf52604b2daaf0a--