cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Damick, Jeffrey" <>
Subject Re: cassandra as session store
Date Tue, 01 Feb 2011 17:38:08 GMT
Are you going to use TTLs to expire the session columns automagically? (we're working on something
similar as well)

On 2/1/11 12:30 PM, "Roshan Dawrani" <> wrote:

Please do keep this discussion on the mailing list and not take it offline. :-)

I will be in the same boat very soon, I think.

It will be great to hear from people who have already gone down this road and used Cassandra
as a session store in a clustered environment.

On Tue, Feb 1, 2011 at 10:56 PM, Kallin Nagelberg <> wrote:
Cool, maybe we can help each other out. I'm using multiple web-apps,
all running in Resin containers. Have you thought about schema or how
to generate sessionIds for cookies?


On Tue, Feb 1, 2011 at 12:22 PM, Sasha Dolgy <> wrote:
> I am working on this tonight with jetty as front end and cassandra as
> backend session store.  Hopefully.
> On 1 Feb 2011 18:19, "Kallin Nagelberg" <> wrote:
>> Hey,
>> I am currently investigating Cassandra for storing what are
>> effectively web sessions. Our production environment has about 10 high
>> end servers behind a load balancer, and we'd like to add distributed
>> session support. My main concerns are performance, consistency, and
>> the ability to create unique session keys. The last thing we would
>> want is users picking up each others sessions. After spending a few
>> days investigating Cassandra I'm thinking of creating a single
>> keyspace with a single super-column-family. The scf would store a few
>> standard columns, and a supercolumn of arbitrary session attributes,
>> like:
>> 0s809sdf8s908sf90s: {
>> prop1: x,
>> created : timestamp,
>> lastAccessed: timestamp,
>> prop2: y,
>> arbirtraryProperties : {
>>             someRandomProperty1:xxyyzz,
>>             someRandomProperty2:xxyyzz,
>>             someRandomProperty3:xxyyzz
>> }
>> Does this sound like a reasonable use case? We are on a tight timeline
>> and I'm currently on the fence about getting something up and running
>> like this on a tight timeline.
>> Thanks,
>> -Kal

View raw message