Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of ruby185@gmail.com designates
 209.85.220.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <da0f2ea3-cd4b-4398-9f00-610872e1c16b@mail>
References: 
 <CAP5HrRb0PK-Nq4d137vSEUx7nitBmm61sm3avN2cmg5HyXsNgA@mail.gmail.com>
	<da0f2ea3-cd4b-4398-9f00-610872e1c16b@mail>
Date: Thu, 25 Aug 2011 14:50:19 -0400
Message-ID: 
 <CAA=a5iO58APMcEzNdQpJ-RCDh+b0J8o=BNdoqXr7unvGu3Z+vQ@mail.gmail.com>
Subject: Re: Is Cassandra suitable for this use case?
From: Ruby Stevenson <ruby185@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

hi Robert -

This is quite interesting. Now CassandraFS on google.code seems
inactive now. I don't see any release out of that.

Do you know if Brisk is considered stable at all or still very experimental?

thanks

Ruby


On Thu, Aug 25, 2011 at 12:44 PM, Robert Jackson
<robertj@promedicalinc.com> wrote:
> I believe this is conceptually similar to what Brisk is doing under
> CassandraFS (HDFS compliant file system on top of cassandra).
>
> Robert Jackson
>
> [1] - https://github.com/riptano/brisk
> ________________________________
> From: "Sasha Dolgy" <sdolgy@gmail.com>
> To: user@cassandra.apache.org
> Sent: Thursday, August 25, 2011 12:36:21 PM
> Subject: Re: Is Cassandra suitable for this use case?
>
> You can chunk the files into pieces and store the pieces in Cassandra...
> Munge all the pieces back together when delivering back to the client...
>
> On Aug 25, 2011 6:33 PM, "Ruby Stevenson" <ruby185@gmail.com> wrote:
>> hi Evgeny
>>
>> I appreciate the input. The concern with HDFS is that it has own
>> share of problems - its name node, which essentially a metadata
>> server, load all files information into memory (roughly 300 MB per
>> million files) and its failure handling is far less attractive ... on
>> top of configuring and maintaining two separate components and two API
>> for handling data. I am still holding out hopes that there might be
>> some better way of go about it?
>>
>> Best Regards,
>>
>> Ruby
>>
>> On Thu, Aug 25, 2011 at 11:10 AM, Evgeniy Ryabitskiy
>> <evgeniy.ryabitskiy@wikimart.ru> wrote:
>>> Hi,
>>>
>>> If you want to store files with partition/replication, you could use
>>> Distributed File System(DFS).
>>> Like http://hadoop.apache.org/hdfs/
>>> or any other:
>>> http://en.wikipedia.org/wiki/Distributed_file_system
>>>
>>> Still you could use Cassandra to store any metadata and filepath in DFS.
>>>
>>> So: Cassandra + HDFS would be my solution.
>>>
>>> Evgeny.
>>>
>>>
>
>