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 dan.kuebrich@gmail.com
 designates 209.85.213.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type;
        b=DX7GHxfzmGy4GoSIH0AHDyaYeJHMwy5aDhj0ijSrVgmWnkxQ40szhKf+pxVm9MkT3A
         KB/NkWSH463sp9WZI62IHz0j2uBEYAXmHgyE7LitxBWMZV0b6EeCQcg8fA0PpNvzQ9Xf
         vOuXXcGMtXlMktniAsNiDwWa7czH1BrImKEDI=
MIME-Version: 1.0
In-Reply-To: <1299185050415-6086307.post@n2.nabble.com>
References: <1299005018456-6078278.post@n2.nabble.com>
 <AANLkTikOQ9ic-jZ2Xse4hNt0wUeFt-ROffij9sHitdYM@mail.gmail.com>
 <1299010248308-6078542.post@n2.nabble.com>
 <AANLkTinZmHqTKJZjfwFjow49N528LnzewuyL+C6jbmwA@mail.gmail.com>
 <1299018977921-6078983.post@n2.nabble.com>
 <AANLkTimTCDvaNXHbZDXyL9sK7S58nsB+zum7LeAT2DuN@mail.gmail.com>
 <1299088026161-6081940.post@n2.nabble.com>
 <1299181763520-6086135.post@n2.nabble.com>
 <AANLkTimNAb9NXHOYB-j4eykiu2ZAvv+SCotrNj48PBsB@mail.gmail.com>
 <1299185050415-6086307.post@n2.nabble.com>
From: Dan Kuebrich <dan.kuebrich@gmail.com>
Date: Thu, 3 Mar 2011 16:02:24 -0500
Message-ID: <AANLkTi=qz-FyOrU59WX=AW=E5oW3n6wOUeeNrwPwhC6b@mail.gmail.com>
Subject: Re: Storing photos, images, docs etc.
To: user@cassandra.apache.org
Cc: mcasandra <mohitanchlia@gmail.com>, cassandra-user@incubator.apache.org
Content-Type: multipart/alternative; boundary=000e0cd59cb802f369049d9a5a39

--000e0cd59cb802f369049d9a5a39
Content-Type: text/plain; charset=ISO-8859-1

It's still maintained: https://github.com/mogilefs/ .  I don't have a good
sense of the community, though we did use it at my last job.

On Thu, Mar 3, 2011 at 3:44 PM, mcasandra <mohitanchlia@gmail.com> wrote:

> Well it's not just metadata that I need to store but also Username,
> profiles,
> followers etc. What I meant was store the location of the images along with
> other information that I described above. And when user queries them then
> pull it from the file sytem.
>
> Most of the high volume sites (facebook, flickr, Digg etc.) currently seem
> to be storing location/URI in the DB and actual blobs(images/docs) etc. on
> the distributed file system. Some have written on their own and some are
> using MogileFS, Lustre etc.
>
> Can't use S3 since the requirement is to keep everything within the network
> so that it's secure and under control.
>
> Initially I thought Cassandra could be used for both row data and as well
> as
> large files. But from what I've read and suggestions that I've got it looks
> like I need to look at distributed file system which is fault taulrent and
> also scales well. After reading online I can come up with only few options
> like lustre, glusterfs and mogileFS to store large files. As you mentioned
> lustreFS needs kernel tweaking/volume creation etc. Still trying to read
> more about glusterFS. And mogileFS last updated date on the site is back in
> 2010 so not sure if it's still widely supported (in case of issues :)).
>
>
> --
> View this message in context:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Storing-photos-images-docs-etc-tp6078278p6086307.html
> Sent from the cassandra-user@incubator.apache.org mailing list archive at
> Nabble.com.
>

--000e0cd59cb802f369049d9a5a39
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It&#39;s still maintained:=A0<a href=3D"https://github.com/mogilefs/">https=
://github.com/mogilefs/</a> . =A0I don&#39;t have a good sense of the commu=
nity, though we did use it at my last job.<br><br><div class=3D"gmail_quote=
">On Thu, Mar 3, 2011 at 3:44 PM, mcasandra <span dir=3D"ltr">&lt;<a href=
=3D"mailto:mohitanchlia@gmail.com">mohitanchlia@gmail.com</a>&gt;</span> wr=
ote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Well it&#39;s not just metadata that I need=
 to store but also Username, profiles,<br>
followers etc. What I meant was store the location of the images along with=
<br>
other information that I described above. And when user queries them then<b=
r>
pull it from the file sytem.<br>
<br>
Most of the high volume sites (facebook, flickr, Digg etc.) currently seem<=
br>
to be storing location/URI in the DB and actual blobs(images/docs) etc. on<=
br>
the distributed file system. Some have written on their own and some are<br=
>
using MogileFS, Lustre etc.<br>
<br>
Can&#39;t use S3 since the requirement is to keep everything within the net=
work<br>
so that it&#39;s secure and under control.<br>
<br>
Initially I thought Cassandra could be used for both row data and as well a=
s<br>
large files. But from what I&#39;ve read and suggestions that I&#39;ve got =
it looks<br>
like I need to look at distributed file system which is fault taulrent and<=
br>
also scales well. After reading online I can come up with only few options<=
br>
like lustre, glusterfs and mogileFS to store large files. As you mentioned<=
br>
lustreFS needs kernel tweaking/volume creation etc. Still trying to read<br=
>
more about glusterFS. And mogileFS last updated date on the site is back in=
<br>
2010 so not sure if it&#39;s still widely supported (in case of issues :)).=
<br>
<font color=3D"#888888"><br>
<br>
--<br>
View this message in context: <a href=3D"http://cassandra-user-incubator-ap=
ache-org.3065146.n2.nabble.com/Storing-photos-images-docs-etc-tp6078278p608=
6307.html" target=3D"_blank">http://cassandra-user-incubator-apache-org.306=
5146.n2.nabble.com/Storing-photos-images-docs-etc-tp6078278p6086307.html</a=
><br>


Sent from the <a href=3D"mailto:cassandra-user@incubator.apache.org">cassan=
dra-user@incubator.apache.org</a> mailing list archive at Nabble.com.<br>
</font></blockquote></div><br>

--000e0cd59cb802f369049d9a5a39--