Mysql?
--
Colin
+1 320 221 9531
On Jul 25, 2013, at 6:08 AM, Derek Andree wrote:
> Yeah, Rob is smart. don't run crap in production. Run what others are
> stable at. If you are running the latest greatest dumbest craziest in prod
> then you ask for fail, and you will get just that.
>
Yeah, Rob is smart. don't run crap in production. Run what others are stable
at. If you are running the latest greatest dumbest craziest in prod then you
ask for fail, and you will get just that.
FAIL
On Jul 24, 2013, at 12:06 PM, Robert Coli wrote:
> A better solution would likely involve
cas 2.0b2
https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/2.0.0-beta2-tentative
> and as a small startup time is our most valuable resource…
use technology you are most familiar with.
On Wed, Jul 24, 2013 at 11:37 AM, Steffen Rusitschka wrote:
> Same thing here... Since #5677 seems to affect a lot of users what do you
> think about releasing a version 1.2.6.1? I can patch myself, yeah, but do I
> want to push this into production? Hmm...
>
A better solution would likely involv
Same thing here... Since #5677 seems to affect a lot of users what do
you think about releasing a version 1.2.6.1? I can patch myself, yeah,
but do I want to push this into production? Hmm...
Am 24.07.2013 18:58, schrieb Paul Ingalls:
Hey Radim,
I knew that it would take a while to stabilize,
veled-compaction
We are read-heavy latency sensitive people
Lots of TTL'ing
Few writes compared to reads.
From: Paul Ingalls [mailto:paulinga...@gmail.com]
Sent: 24 July 2013 17:43
To: user@cassandra.apache.org
Subject: Re: disappointed
Hi Chris,
Thanks for the response!
Wh
Hey Radim,
I knew that it would take a while to stabilize, which is why I waited 1/2 a
year before giving it a go. I guess I was just surprised that 6 months wasn't
long enough…
I'll have to look at the differences between 1.2 and 2.0. Is there a good
resource for checking that?
Your experi
Hi Chris,
Thanks for the response!
What kind of challenges did you run into that kept you from using collections?
I currently and running 4 physical nodes, same as I was with case 1.1.6. I'm
using size tiered compaction. Would changing to level tiered with a large
minimum make a big differen
Same type of error, but I'm not currently using TTL's. I am, however,
generating a lot of tombstones as I add elements to collections….
On Jul 24, 2013, at 6:42 AM, Fabien Rousseau wrote:
> Hi Paul,
>
> Concerning large rows which are not compacting, I've probably managed to
> reproduce you
From my limited experience I think Cassandra is a dangerous choice for
an young limited funding/experience start-up expecting to scale fast.
Its not dangerous, just do not try to be smart and follow what other big
cassandra users like twitter, netflix, facebook, etc are using. If they
are st
Hi Paul,
Concerning large rows which are not compacting, I've probably managed to
reproduce your problem.
I suppose you're using collections, but also TTLs ?
Anyway, I opened an issue here :
https://issues.apache.org/jira/browse/CASSANDRA-5799
Hope this helps
2013/7/24 Christopher Wirt
> Hi
Hi Paul,
Sorry to hear you're having a low point.
We ended up not using the collection features of 1.2.
Instead storing a compressed string containing the map and handling client
side.
We only have fixed schema short rows so no experience with large row
compaction.
File descriptor
12 matches
Mail list logo
