From user-return-12716-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Tue Feb 01 20:21:29 2011 Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 96941 invoked from network); 1 Feb 2011 20:21:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Feb 2011 20:21:29 -0000 Received: (qmail 65063 invoked by uid 500); 1 Feb 2011 20:21:27 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 65010 invoked by uid 500); 1 Feb 2011 20:21:26 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 65002 invoked by uid 99); 1 Feb 2011 20:21:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Feb 2011 20:21:26 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of kallin.nagelberg@gmail.com designates 209.85.210.172 as permitted sender) Received: from [209.85.210.172] (HELO mail-iy0-f172.google.com) (209.85.210.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Feb 2011 20:21:22 +0000 Received: by iyi42 with SMTP id 42so6961782iyi.31 for ; Tue, 01 Feb 2011 12:21:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type:content-transfer-encoding; bh=rIGjdYvyg08pTDbulLez6+Ia5EMEjbBPFb5P7IJXmjc=; b=wLoECnYRd1EPT4I5vYx8L6BxSUXZdcViYeITDY8RHVhDwAn4r0jSdOJgto9yRh1uHh Jh9ettzG1XQekQTl+Dsshri9wu8qSjI5sk92OpCxsb4UnEpWMu7+n7n5/IXrCCeaP0/h /9RA6B4f+Kf+wZz93DG0rgM2DkKRKO4b9Rcrs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=UsqpUr4soJzsYuMIIew7p6lG5cd5ay8vNH5XDwL6e6QjQJr3dGdW+jrI25bIQB+bEL awGV8mMs2Mvh+Jt+CYrFcPkBAiVolsNWJFobFxqiEcpiBCN4GlRGghFOWbYqqL8uWskU LFH58/zJCPRU4kXrfxilYeEEIserFOlSqvas8= Received: by 10.231.206.143 with SMTP id fu15mr8866270ibb.3.1296591661207; Tue, 01 Feb 2011 12:21:01 -0800 (PST) MIME-Version: 1.0 Received: by 10.231.13.72 with HTTP; Tue, 1 Feb 2011 12:20:41 -0800 (PST) In-Reply-To: References: <1296582141589-5981961.post@n2.nabble.com> <1296583033554-5982024.post@n2.nabble.com> From: Kallin Nagelberg Date: Tue, 1 Feb 2011 15:20:41 -0500 Message-ID: Subject: Re: cassandra as session store To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable nvm on the persistence, it seems like it does support it: 'Since version 1.1 the safer alternative is an append-only file (a journal) that is written as operations modifying the dataset in memory are processed. Redis is able to rewrite the append-only file in the background in order to avoid an indefinite growth of the journal.' This thread probably shouldn't digress too much from Cassandra's suitability for session management though.. On Tue, Feb 1, 2011 at 3:10 PM, Kallin Nagelberg wrote: > Reddis seems neat, but a couple issues: > > - It's 'persistence' is more of a timed backup. You are not guaranteed > the latest results on disk. > - no real 'clustering'. It has a master/slave system. > > Hard to say if those are deal breakers at this point, but the API for > it seems nice. > > On Tue, Feb 1, 2011 at 1:48 PM, Kallin Nagelberg > wrote: >> Hmm, looking at redis now. The built in time to live functionality >> would be nice to have.. >> >> On Tue, Feb 1, 2011 at 1:34 PM, Colin Vipurs wrote= : >>> Wouldn't something like Redis be a better fit than Cassandra? >>> >>> On Tue, Feb 1, 2011 at 6:16 PM, Tong Zhu wrote: >>>> If it is a really session data, which will be active for a short time,= a few hours, and it is OK to lose them, memcached is a better solution. I = were using it when I was in Yahoo. >>>> >>>> Tong >>>> >>>> -----Original Message----- >>>> From: buddhasystem [mailto:potekhin@bnl.gov] >>>> Sent: Tuesday, February 01, 2011 9:57 AM >>>> To: cassandra-user@incubator.apache.org >>>> Subject: Re: cassandra as session store >>>> >>>> >>>> For completeness: >>>> >>>> http://stackoverflow.com/questions/3746685/running-django-site-in-mult= iserver-environment-how-to-handle-sessions >>>> http://docs.djangoproject.com/en/dev/topics/http/sessions/#using-cache= d-sessions >>>> >>>> I guess your approach does make sense, one only wishes that the servle= t in >>>> question did more work for you. If I read correctly, Django can cache >>>> sessions transparently in memcached. So memcached mecomes your Session >>>> Management System. Is it better or worse than Cassandra? My feeling is= that >>>> it's probably faster and easier to set up. >>>> >>>> >>>> -- >>>> View this message in context: http://cassandra-user-incubator-apache-o= rg.3065146.n2.nabble.com/cassandra-as-session-store-tp5981871p5982024.html >>>> Sent from the cassandra-user@incubator.apache.org mailing list archive= at Nabble.com. >>>> >>>> >>>> This message and any attachments contain information that may be RMS I= nc. confidential and/or privileged. =A0If you are not the intended recipien= t (or authorized to receive for the intended recipient), and have received = this message in error, any use, disclosure or distribution is strictly proh= ibited. =A0 If you have received this message in error, please notify the s= ender immediately by replying to the e-mail and permanently deleting the me= ssage from your computer and/or storage system. >>>> >>> >>> >>> >>> -- >>> Maybe she awoke to see the roommate's boyfriend swinging from the >>> chandelier wearing a boar's head. >>> >>> Something which you, I, and everyone else would call "Tuesday", of cour= se. >>> >> >