Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 74769 invoked from network); 6 Jul 2010 23:14:14 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 6 Jul 2010 23:14:14 -0000 Received: (qmail 57655 invoked by uid 500); 6 Jul 2010 23:14:13 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 57622 invoked by uid 500); 6 Jul 2010 23:14:12 -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 57614 invoked by uid 99); 6 Jul 2010 23:14:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Jul 2010 23:14:12 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of MATT.SU@morningstar.com designates 216.228.224.34 as permitted sender) Received: from [216.228.224.34] (HELO mx89.morningstar.com) (216.228.224.34) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 06 Jul 2010 23:14:05 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB1D60.D496C2CE" Subject: RE: Digg 4 Preview on TWiT Date: Tue, 6 Jul 2010 18:13:16 -0500 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Digg 4 Preview on TWiT Thread-Index: AcsdW+VQPVBLTL5QQDmVRDHkWKjeKgAA5uuA References: <2B4B52565669304C979DC60E52AA3F9B022CC04DC8@spnvm1183.bud.bpa.gov><1277743872.11218.25.camel@erebus.lan><1278245675.3878.4.camel@dehora-laptop><1278344422.3283.18.camel@erebus.lan><4C3306A3.70804@fourkitchens.com><1278447567.2420.288.camel@dehora-laptop> From: "Matt Su" To: , X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. ------_=_NextPart_001_01CB1D60.D496C2CE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thanks for all your guys' information. This thread make us raised a concern: we choose Cassandra because = FB,Twitter,Digg are using them, and we're doubting whether Cassandra is = definitely trustable. The question is what action will we take, if after a few time, these big = tech company really start to leave Cassandra. =20 Will we have the confidence to trust Apache Cassandra, instead of = following these tech company's storage solution. :-) =20 Thanks and Regards. ________________________________ From: Prashant Malik [mailto:pmalik@gmail.com]=20 Sent: Tuesday, July 06, 2010 5:36 PM To: user@cassandra.apache.org; bill@dehora.net Subject: Re: Digg 4 Preview on TWiT =20 I have gone through the appropriate channel here at FB to make sure = that=20 the correct information is presented. the article has now been updated to=20 " (Update: just for reference, we're told via email that Facebook, "no = longer contributes to nor uses Cassandra." Update 2: we are now being = told - and Facebook has confirmed - that Cassandra is actually still = employed by the company for, among other things, Inbox Search.) " Thanks Prashant On Tue, Jul 6, 2010 at 1:19 PM, Bill de h=D3ra wrote: Nonetheless, thanks for clearing that one up. And that's some serious volume you've got there :) Bill On Tue, 2010-07-06 at 12:01 -0700, Prashant Malik wrote: > This is a ridiculous statement by some newbie I guess , We today have > a 150 node Cassandra cluster running Inbox search supporting close to > 500M users > and over 150TB of data growing rapidly everyday. > > I am on pager for this monster :) so its pretty funny to hear this > statement. > > - Prashant > > On Tue, Jul 6, 2010 at 6:21 AM, Avinash Lakshman > wrote: > FB Inbox Search still runs on Cassandra and will continue to > do so. I should know since I maintain it :). > > Cheers > Avinash > > > > On Tue, Jul 6, 2010 at 3:34 AM, David Strauss > wrote: > On 2010-07-05 15:40, Eric Evans wrote: > > On Sun, 2010-07-04 at 13:14 +0100, Bill de h=D3ra > wrote: > >> This person's understanding is that Facebook 'no > longer contributes to > >> nor uses Cassandra.': > >> > >> > = http://redmonk.com/sogrady/2010/05/17/beyond-cassandra/ > > > > Last I heard, Facebook was still using Cassandra for > what they had > > always used it for, Inbox Search. Last I heard, > there were no plans in > > place to change that. > > > I had the opportunity to talk with some Facebook > infrastructure > engineers in San Francisco over the past few weeks. > They are no longer > using Cassandra, even for inbox search. > > Inbox search was intended to be an initial push for > using Cassandra more > broadly, not the primary target of the Cassandra > design. Unfortunately, > Facebook's engineers later decided that Cassandra > wasn't the right > answer to the right question for Facebook's purposes. > > That decision isn't an indictment of Cassandra's > capability; it's > confirmation that Cassandra isn't everything to > everyone. But we already > knew that. :-) > > -- > David Strauss > | david@fourkitchens.com > | +1 512 577 5827 [mobile] > Four Kitchens > | http://fourkitchens.com > | +1 512 454 6659 [office] > | +1 512 870 8453 [direct] > > > > =20 ------_=_NextPart_001_01CB1D60.D496C2CE Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Thanks for = all your guys’ information.

This thread = make us raised a concern: we choose Cassandra because FB,Twitter,Digg are using = them, and we’re doubting whether Cassandra is definitely = trustable.

The question = is what action will we take, if after a few time, these big tech company really start = to leave Cassandra.

 

Will we have = the confidence to trust Apache Cassandra, instead of following these tech = company’s storage solution. J

 

Thanks and = Regards.

From: = Prashant Malik [mailto:pmalik@gmail.com]
Sent: Tuesday, July 06, = 2010 5:36 PM
To: = user@cassandra.apache.org; bill@dehora.net
Subject: Re: Digg 4 = Preview on TWiT

 

I have gone = through the appropriate channel  here  at FB  to make sure that
the correct information is presented.

the article has now been updated to

" (Update: just = for reference, we’re told via email that Facebook, “no longer contributes to nor uses Cassandra.” Update 2: we are now being told – and Facebook has confirmed = – that Cassandra is actually still employed by the company for, among = other things, Inbox Search.) "

Thanks
Prashant

On Tue, Jul 6, 2010 at 1:19 PM, Bill de h=D3ra <bill@dehora.net> = wrote:

Nonetheless, thanks for clearing that one up. And that's some = serious
volume you've got there :)

Bill


On Tue, 2010-07-06 at 12:01 -0700, Prashant Malik wrote:
> This is a ridiculous statement by some newbie I guess , We today = have
> a 150 node Cassandra cluster running Inbox search supporting close = to
> 500M users
> and over 150TB of data  growing rapidly everyday.
>
> I am on pager for this monster :) so its pretty funny to hear = this
> statement.
>
> - Prashant
>

> On Tue, = Jul 6, 2010 at 6:21 AM, Avinash Lakshman
> <avinash.lakshman@gmail.com= > wrote:
>         FB Inbox Search still runs on Cassandra = and will continue to
>         do so. I should know since I maintain = it :).
>
>         Cheers
>         Avinash
>
>
>
>         On Tue, Jul 6, 2010 at 3:34 AM, David = Strauss
>         <david@fourkitchens.com> wrote:
>                 On = 2010-07-05 15:40, Eric Evans wrote:
>                 > On = Sun, 2010-07-04 at 13:14 +0100, Bill de h=D3ra
>                 wrote:
>                 >> = This person's understanding is that Facebook 'no
>                 longer = contributes to
>                 >> = nor uses Cassandra.':
>                 = >>
>                 = >>
>                 http://redmonk.com/sogrady/2010/05/17/beyond-cassandra/=
>                 >
>                 > Last I = heard, Facebook was still using Cassandra for
>                 what they = had
>                 > always = used it for, Inbox Search. Last I heard,
>                 there were = no plans in
>                 > place = to change that.
>
>
>                 I had the = opportunity to talk with some Facebook
>                 = infrastructure
>                 engineers = in San Francisco = over the past few weeks.
>                 They are no = longer
>                 using = Cassandra, even for inbox search.
>
>                 Inbox = search was intended to be an initial push for
>                 using = Cassandra more
>                 broadly, = not the primary target of the Cassandra
>                 design. Unfortunately,
>                 Facebook's engineers later decided that Cassandra
>                 wasn't the = right
>                 answer to = the right question for Facebook's purposes.
>
>                 That = decision isn't an indictment of Cassandra's
>                 capability; = it's
>                 = confirmation that Cassandra isn't everything to
>                 everyone. = But we already
>                 knew that. = :-)
>
>                 --
>                 David = Strauss
>                   | david@fourkitchens.com
>                   | +1 = 512 577 5827 [mobile]
>                 Four = Kitchens
>                   | http://fourkitchens.com
>                   | +1 = 512 454 6659 [office]
>                   | +1 = 512 870 8453 [direct]
>
>
>
>

 

------_=_NextPart_001_01CB1D60.D496C2CE--