It would be really great to look at your slides. Do you have any plans to
share your presentation?
On Sat, Jun 9, 2012 at 1:14 AM, Віталій Тимчишин wrote:
> Thanks a lot. I was not sure if coordinator somehow tries to "roll-back"
> transactions that failed to reach it's consistency level.
> (Yet
But I think it's bad idea, since hot data will be evenly distributed
between multiple sstables and filesystem pages.
On Thu, May 31, 2012 at 1:08 PM, crypto five wrote:
> You may also consider disabling key/row cache at all.
> 1mm rows * 400 bytes = 400MB of data, can easily be in fs
You may also consider disabling key/row cache at all.
1mm rows * 400 bytes = 400MB of data, can easily be in fs cache, and you
will access your hot keys with thousands of qps without hitting disk at all.
Enabling compression can make situation even better.
On Thu, May 31, 2012 at 12:01 PM, Gurpree
umn families" in your message tells it's
> possibly the same problem.
> The issue is that column families that gets full row deletes only do not
> get ANY SINGLE dirty byte accounted and so can't be picked by flusher. Any
> ratio can't help simply because it is multipl
igher than 64 something
is probably broken.", looks like it's probably the problem.
Not sure how to investigate it.
2012/4/23 Віталій Тимчишин
> See https://issues.apache.org/jira/browse/CASSANDRA-3741
> I did post a fix there that helped me.
>
>
> 2012/4/24 crypto five
&
Hi,
I have 50 millions of rows in column family on 4G RAM box. I allocatedf 2GB
to cassandra.
I have program which is traversing this CF and cleaning some data there, it
generates about 20k delete statements per second.
After about of 3 millions deletions cassandra stops responding to queries:
it
