Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 20831 invoked from network); 15 Apr 2010 02:33:22 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 15 Apr 2010 02:33:22 -0000 Received: (qmail 36390 invoked by uid 500); 15 Apr 2010 02:33:21 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 36322 invoked by uid 500); 15 Apr 2010 02:33:21 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 36314 invoked by uid 99); 15 Apr 2010 02:33:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Apr 2010 02:33:21 +0000 X-ASF-Spam-Status: No, hits=1.7 required=10.0 tests=AWL,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of miguelitovert@gmail.com designates 209.85.217.172 as permitted sender) Received: from [209.85.217.172] (HELO mail-gx0-f172.google.com) (209.85.217.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Apr 2010 02:33:15 +0000 Received: by gxk20 with SMTP id 20so48008gxk.8 for ; Wed, 14 Apr 2010 19:32:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:content-type; bh=VS+JQrQDKovIe+rb+6SXJxAFnmdMs31G7w8Um8Rj9NY=; b=GBWOg44P3Vm7tQ2cfcRemIggs5jMmyNUcbuhg/IJXT6LbhNQkK9Q1P8Olf3CNnU0Ds JdA3qBy5alG+026msvdM8qIdm6rEJD+oTYsBT+0kJjBkdmBjOpiBAR8+snpYj9tyqaXW g8yZ/HRuOSRdHGwwX5J5HMirYiMHHF5M168ko= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=un/DbthVja5aq28+jdOS6ZtfK00ThD/heVmwt2RXZNrcJzRw6boUKMtY3mt/YIsEZo g0nB5ts4TE5djRPnU8sxHx8gjyrAWZTIVIJkq3RKMu8Qlr/1tNYzQMe32QoHfLsB6O+G +Yn6eL4xdlb9LXZme7jlx3LZfpduoQB9/jSvQ= MIME-Version: 1.0 Received: by 10.150.138.17 with HTTP; Wed, 14 Apr 2010 19:32:54 -0700 (PDT) In-Reply-To: References: Date: Wed, 14 Apr 2010 21:32:54 -0500 Received: by 10.150.165.3 with SMTP id n3mr7445785ybe.47.1271298774115; Wed, 14 Apr 2010 19:32:54 -0700 (PDT) Message-ID: Subject: Re: Is that possible to write a file system over Cassandra? From: Miguel Verde To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=000e0cd5637ed5a6f904843d4fff --000e0cd5637ed5a6f904843d4fff Content-Type: text/plain; charset=ISO-8859-1 On Wed, Apr 14, 2010 at 9:26 PM, Avinash Lakshman < avinash.lakshman@gmail.com> wrote: > OPP is not required here. You would be better off using a Random > partitioner because you want to get a random distribution of the metadata. Not required, certainly. However, it strikes me that 1 cluster is better than 2, and most consumers of a filesystem would expect to be able to get an ordered listing or tree of the metadata which is easy using the OPP row key pattern listed previously. You could still do this with the Random partitioner using column names in rows to describe the structure but the current compaction limitations could be an issue if a branch becomes too large, and you'd still have a root row hotspot (at least in the schema which comes to mind). --000e0cd5637ed5a6f904843d4fff Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Wed, Apr 14, 2010 at 9:26 PM, Avinash Lakshma= n <avina= sh.lakshman@gmail.com> wrote:
OPP is not required here. You wo= uld be better off using a Random partitioner because you want to get a rand= om distribution of the metadata.
=A0
Not required, certainly.=A0 However, it strikes me that 1 cluster is b= etter than 2, and most consumers of a filesystem would expect to be able to= get an ordered listing or tree of the metadata which is easy using the OPP= row key pattern listed previously.=A0 You could still do this=A0with the R= andom partitioner using=A0column names in rows to describe the structure bu= t the current compaction limitations could be an issue if a branch becomes = too large, and you'd still have a root row hotspot (at least in the sch= ema which comes to mind).
--000e0cd5637ed5a6f904843d4fff--