We're using Cassandra as the back end for a home grown session
management system. That system was originally built back in 2005 using
BerkelyDB/Java and a data distribution system that used UDP multicast.
Maintenance was becoming increasingly painful.
I wrote a prototype replacement service using
Jonathan pointed out in another thread that it looks like I'm running
into CASSANDRA-2059, where secondary files are not being properly
deleted. My production data set at any given time is less than 100 MB
in size, but the Cassandra data directories on each instance are using
30 to 40 times as much
We have an application that stores session data in Cassandra. The
session data needs to be deleted after, say, one hour of inactivity. The
CASSANDRA-699 TTL update in 0.7 looks like it will work very well for
that.
However, we have a few scenarios where some session data will be
retrieved frequent
The ticket is here: https://issues.apache.org/jira/browse/CASSANDRA-884
I've attached a patch there that seems to fix the problem.
Has anybody else seen this behavior?
> That would be a bug, not intended behavior. Can you open a ticket?
>
> On Fri, Mar 12, 2010 at 11:48 AM, Omer
t;
>>> That would be a bug, not intended behavior. Can you open a ticket?
>>>
>>> On Fri, Mar 12, 2010 at 11:48 AM, Omer van der Horst Jansen
>>> wrote:
>>> > I've noticed that both 0.5.1 and 0.6b2 return (ReplicationFactor)
>
