cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5348) Remove row cache until we can replace it with something better
Date Mon, 25 Mar 2013 21:33:16 GMT


Jason Brown commented on CASSANDRA-5348:

I agree with Sylvain on this. We've spent a lot of time and effort pitching row cacheing,
and it might be a bit of a kick in the shins to pull it out on those use who've decided to
give it a shot (and are using it successfully). There are a few (few, mind you) reasonable
uses of row cache here at NFLX, and those users are happy with it.

I'll agree about the education piece, but I think it would be good to have our rewrite story
reasonably organized before asking the community to avoid row caches. That way, we can have
a smoother transition for users.

Unless the effort of working around the current implementation is a complete road block to
getting the new hotness up and running, I think we should keep the existing solution around.
Making the rewrite a priority for 2.1 gets a +1 from me.
> Remove row cache until we can replace it with something better
> --------------------------------------------------------------
>                 Key: CASSANDRA-5348
>                 URL:
>             Project: Cassandra
>          Issue Type: Task
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Vijay
>             Fix For: 2.0
> The row (partition) cache easily does more harm than good.  People expect it to act like
a query cache but it is very different than that, especially for the wide partitions that
are so common in Cassandra data models.
> Making it off-heap by default only helped a little; we still have to deserialize the
partition to the heap to query it.
> Ultimately we can add a better cache based on the ideas in CASSANDRA-1956 or CASSANDRA-2864,
but even if we don't get to that until 2.1, removing the old row cache for 2.0 is a good idea.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message