; to all the new nodes that come online(cassandra actually has a very data
>> center/rack aware topology to transfer data correctly to not use up all
>> bandwidth unecessarily…I am not sure mongodb has that). Anyways, just food
>> for thought.
>>
>> From: aaron morton
>> mai
ashes but the data
is still good on the drives, it would just mean bringing up the node using the
same storage ? would this not be fast…?
From: aaron morton [mailto:aa...@thelastpickle.com]
Sent: 21 February 2013 11:46
To: user@cassandra.apache.org
Subject: Re: cassandra vs. mongodb quick que
dra.apache.org>>
> Date: Monday, February 18, 2013 1:39 PM
> To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
> mailto:user@cassandra.apache.org>>, Vegard Berget
> mailto:p...@fantasista.no>>
> Subject: Re: cassandra vs. mongodb quick question
2013 1:39 PM
> To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <
> user@cassandra.apache.org<mailto:user@cassandra.apache.org>>, Vegard
> Berget mailto:p...@fantasista.no>>
> Subject: Re: cassandra vs. mongodb quick question
>
>
gt;>
>> From: Bryan Talbot mailto:btal...@aeriagames.com>>
>> Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
>> mailto:user@cassandra.apache.org>>
>> Date: Wednesday, February 20, 2013 1:04 PM
>> To: "user@cassandra.apache.o
ailto:user@cassandra.apache.org>" <
> user@cassandra.apache.org<mailto:user@cassandra.apache.org>>
> Date: Wednesday, February 20, 2013 1:04 PM
> To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <
> user@cassandra.apache.org<mailto:user@cassa
g>>
Date: Wednesday, February 20, 2013 1:04 PM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: cassandra vs. mongodb quick question(good additional info)
This calculation is incorrect btw. 10,000 GB
This calculation is incorrect btw. 10,000 GB transferred at 1.25 GB / sec
would complete in about 8,000 seconds which is just 2.2 hours and not 5.5
days. The error is in the conversion (1hr/60secs) which is off by 2 orders
of magnitude since (1hr/3600secs) is the correct conversion.
-Bryan
On
19, 2013 7:02:56 AM
Subject: Re: cassandra vs. mongodb quick question(good additional info)
The 40 TB use case you heard about is probably one 40TB mysql machine
that someone migrated to mongo so it would be "web scale" Cassandra is
NOT good with drives that big, get a blade center or a
assandra.apache.org>"
> mailto:user@cassandra.apache.org>>
> Date: Monday, February 18, 2013 1:39 PM
> To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
> mailto:user@cassandra.apache.org>>, Vegard Berget
> mailto:p...@f
user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>, Vegard Berget
mailto:p...@fantasista.no>>
Subject: Re: cassandra vs. mongodb quick question
My experience is repair of 300GB compressed data takes longer than 300GB of
uncompressed, but I cannot point to an exact nu
;
> - Original Message -
> From:
> user@cassandra.apache.org
>
> To:
>
> Cc:
>
> Sent:
> Mon, 18 Feb 2013 08:41:25 +1300
> Subject:
> Re: cassandra vs. mongodb quick question
>
>
> If you have spinning disk and 1G networking and no virtual nodes, I
Subject:Re: cassandra vs. mongodb quick question
If you have spinning disk and 1G networking and no virtual nodes, I
would still say 300G to 500G is a soft limit.
If you are using virtual nodes, SSD, JBOD disk configuration or
faster networking you may go higher.
The limiting factors are the
If you have spinning disk and 1G networking and no virtual nodes, I would still
say 300G to 500G is a soft limit.
If you are using virtual nodes, SSD, JBOD disk configuration or faster
networking you may go higher.
The limiting factors are the time it take to repair, the time it takes to
rep
So I found out mongodb varies their node size from 1T to 42T per node depending
on the profile. So if I was going to be writing a lot but rarely changing
rows, could I also use cassandra with a per node size of +20T or is that not
advisable?
Thanks,
Dean
n have profound in effects in operation and performance. Thus someone
>> trying to paper over 6 technologies and compare them with a few bullet
>> points is really doing the world an injustice.
>> On Tue, Dec 27, 2011 at 5:01 PM, Igor Lino wrote:
>>
>> Hi!
>&
Hi!
>
>I was trying to get an understanding of the real strengths of
> Cassandra against other competitors. Its actually not that simple and
> depends a lot on details on the actual requirements.
>
>Reading the following comparison:
>http://kkovacs.eu/cassand
itors. Its actually not that simple and depends a lot on
details on the actual requirements.
Reading the following comparison:
http://kkovacs.eu/cassandra-vs-mongodb-vs-couchdb-vs-redis
It felt like the description of Cassandra painted a limiting picture of
its capabili
> Also when comparing these technologies very subtle differences in design
> have profound in effects in operation and performance. Thus someone trying
> to paper over 6 technologies and compare them with a few bullet points is
> really doing the world an injustice.
+1. Same goes for 99% of all be
and depends a lot
> on details on the actual requirements.
>
> Reading the following comparison:
> http://kkovacs.eu/cassandra-vs-mongodb-vs-couchdb-vs-redis
>
> It felt like the description of Cassandra painted a limiting picture of
> its capabilities. Is there any Cassandra expe
Hi!
I was trying to get an understanding of the real strengths of Cassandra against
other competitors. Its actually not that simple and depends a lot on details on
the actual requirements.
Reading the following comparison:
http://kkovacs.eu/cassandra-vs-mongodb-vs-couchdb-vs-redis
It felt
Having participated in the design of a few of these systems being mentioned,
I'll chime in here and point out that the combination of Flume and Hive
makes CDH3 very useful for log processing and that use case is directly in
the wheelhouse of the system, especially for large collections of log files
> "As a result, we designed and built Flume...
> (I wonder if this could deliver into Cassanda :) )
Yes - apparently it's pretty easy to do - I was thinking of doing it but
haven't found the time yet.
https://issues.cloudera.org//browse/FLUME-20
On Jul 28, 2010, at 4:30 PM, Aaron Morton wrote:
If you are looking to store web logs and then do ad hoc queries you might/should be using Hadoop (depending on how big your logs are) I agree, take a look at the Cloudera Hadopp 3 CDH3, they include an app called Flume for moving data..."As a result, we designed and built Flume. Flume is a distribu
If you are looking to store web logs and then do ad hoc queries you
might/should be using Hadoop (depending on how big your logs are)
While MongoDB has MapReduce (built in) it is there to simulate SQL GROUP BY
and not for large scale analytics by any means.
MongoDB uses a global read/write lock p
They have approximately nothing in common. And, no, Cassandra is
definitely not dying off.
On Tue, Jul 27, 2010 at 8:14 AM, Mark wrote:
> Can someone quickly explain the differences between the two? Other than the
> fact that MongoDB supports ad-hoc querying I don't know whats different. It
> al
On 7/27/10 12:42 PM, Dave Gardner wrote:
There are quite a few differences. Ultimately it depends on your use
case! For example Mongo has a limit on the maximum "document" size of
4MB, whereas with Cassandra you are not really limited to the volume
of data/columns per-row (I think there maybe a l
There are quite a few differences. Ultimately it depends on your use
case! For example Mongo has a limit on the maximum "document" size of
4MB, whereas with Cassandra you are not really limited to the volume
of data/columns per-row (I think there maybe a limit of 2GB perhaps;
basically none)
Anoth
Also, google trends is only a measure of what terms people are
searching for. To equate this directly to growth would be misleading.
Tue, Jul 27, 2010 at 12:27 PM, Drew Dahlke wrote:
> There's a good post on stackoverflow comparing the two
> http://stackoverflow.com/questions/2892729/mongodb-vs-
There's a good post on stackoverflow comparing the two
http://stackoverflow.com/questions/2892729/mongodb-vs-cassandra
It seems to me that both projects have pretty vibrant communities behind them.
On Tue, Jul 27, 2010 at 11:14 AM, Mark wrote:
> Can someone quickly explain the differences betwee
Can someone quickly explain the differences between the two? Other than
the fact that MongoDB supports ad-hoc querying I don't know whats
different. It also appears (using google trends) that MongoDB seems to
be growing while Cassandra is dying off. Is this the case?
Thanks for the help
31 matches
Mail list logo
