Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-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 7766B9111 for ; Thu, 9 Feb 2012 04:59:05 +0000 (UTC) Received: (qmail 18767 invoked by uid 500); 9 Feb 2012 04:59:01 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 18388 invoked by uid 500); 9 Feb 2012 04:58:55 -0000 Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-user@hadoop.apache.org Delivered-To: mailing list common-user@hadoop.apache.org Received: (qmail 16808 invoked by uid 99); 9 Feb 2012 04:58:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Feb 2012 04:58:50 +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 edlinuxguru@gmail.com designates 209.85.214.176 as permitted sender) Received: from [209.85.214.176] (HELO mail-tul01m020-f176.google.com) (209.85.214.176) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Feb 2012 04:58:41 +0000 Received: by obbwd18 with SMTP id wd18so2647094obb.35 for ; Wed, 08 Feb 2012 20:58:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=sZomVRnkY9MFNL/xDrQIn+W+ELKJwO3PIKlJv5X2Ijw=; b=Y4QKFjOEbQB0hdwOWzzlrYXpGyZmDqb4kwDTLMe4vPBxxzx/58wxJPXGWOGH5HJ+VQ H0YvG44hNpVSwWYAWEzxAJ/Z1TPpCiD0w7+0ofZhKoqAbWnXpIJWfN2yYHi0uLN8QuPd 2gs/Wz9ZyNijFZBuqEW3iaKk26dj0/pI0TK1Y= MIME-Version: 1.0 Received: by 10.50.193.195 with SMTP id hq3mr289283igc.18.1328763474918; Wed, 08 Feb 2012 20:57:54 -0800 (PST) Received: by 10.42.197.1 with HTTP; Wed, 8 Feb 2012 20:57:54 -0800 (PST) In-Reply-To: References: Date: Wed, 8 Feb 2012 23:57:54 -0500 Message-ID: Subject: Re: Brisk vs Cloudera Distribution From: Edward Capriolo To: "common-user@hadoop.apache.org" Cc: "cdh-user@cloudera.org" Content-Type: multipart/alternative; boundary=14dae9340df5e9bc6004b880da16 X-Virus-Checked: Checked by ClamAV on apache.org --14dae9340df5e9bc6004b880da16 Content-Type: text/plain; charset=ISO-8859-1 Hadoop can work on a number of filessytems hdfs , s3. Local files. Brisk file system is known as cfs. Cfs stores all block and meta data in cassandra. Thus it does not use a name node. Brisk fires up a jobtracker automatically as well. Brisk also has a hivemeta store backed by cassandra so takes away that spof. Brisk snappy compresses all data so you may not need to use compression or sequence files. Performance wise I have gotten comparable numbers with tera sort and tera gen. But the system work vastly differently and likely it scales differently. The hive integration is solid. Not sure what the biggest cluster is or making other vague performance claims. Brisk is not active anymore the commercial product is dse. There is a github fork of brisk however. On Wednesday, February 8, 2012, rk vishu wrote: > Hello All, > > Could any one help me understand pros and cons of Brisk vs Cloudera Hadoop > (DHFS + HBASE) in terms of functionality and performance? > Wanted to keep aside the single point of failure (NN) issue while comparing? > Are there any big clusters in petabytes using brisk in production? How is > the performance comparision CFS vs HDFS? How is Hive integration? > > Thanks and Regrds > RK > --14dae9340df5e9bc6004b880da16--