Return-Path: Delivered-To: apmail-incubator-cassandra-dev-archive@minotaur.apache.org Received: (qmail 71126 invoked from network); 10 Mar 2010 14:21:01 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 10 Mar 2010 14:21:01 -0000 Received: (qmail 6407 invoked by uid 500); 10 Mar 2010 14:20:31 -0000 Delivered-To: apmail-incubator-cassandra-dev-archive@incubator.apache.org Received: (qmail 6328 invoked by uid 500); 10 Mar 2010 14:20:30 -0000 Mailing-List: contact cassandra-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-dev@incubator.apache.org Delivered-To: mailing list cassandra-dev@incubator.apache.org Received: (qmail 6320 invoked by uid 99); 10 Mar 2010 14:20:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Mar 2010 14:20:30 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=HK_RANDOM_ENVFROM,RCVD_NUMERIC_HELO,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gcdcd-cassandra-dev@m.gmane.org designates 80.91.229.12 as permitted sender) Received: from [80.91.229.12] (HELO lo.gmane.org) (80.91.229.12) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Mar 2010 14:20:28 +0000 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1NpMlX-0003PE-Ek for cassandra-dev@incubator.apache.org; Wed, 10 Mar 2010 15:20:03 +0100 Received: from 38.98.147.130 ([38.98.147.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 10 Mar 2010 15:20:03 +0100 Received: from tzz by 38.98.147.130 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 10 Mar 2010 15:20:03 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: cassandra-dev@incubator.apache.org From: Ted Zlatanov Subject: Re: thinking about dropping hinted handoff Date: Wed, 10 Mar 2010 08:16:52 -0600 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Lines: 23 Message-ID: <878wa0b6sr.fsf@lifelogs.com> References: <7c5131fa1001271112h7f51bc6dhd01ef77480183f25@mail.gmail.com> <1264621715.247628425@192.168.2.227> <7c5131fa1001271202g7883e03bj3b03ab37846827ff@mail.gmail.com> <7c5131fa1002221153n2b820454qed3b15b3ff1ae0c7@mail.gmail.com> <3466a8ed1002221212x5813a12fm5f26b1d948f8602e@mail.gmail.com> <87y6ijztwj.fsf@lifelogs.com> <87sk8orsfq.fsf@lifelogs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 38.98.147.130 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6;d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1.91 (gnu/linux) Cancel-Lock: sha1:QheaCOxT6rqoA109ZToaFFmO2oc= On Fri, 26 Feb 2010 08:18:49 -0600 Ted Zlatanov wrote: TZ> On Tue, 23 Feb 2010 12:30:52 -0600 Ted Zlatanov wrote: > Can a Cassandra node be made read-only (as far as clients know)? TZ> I realized I have another use case for read-only access besides backups: TZ> On our network we have Cassandra readers, writers, and analyzers TZ> (read+write). The writers and analyzers can run anywhere. The readers TZ> can run anywhere too. I don't want the readers to have write access but TZ> they should be able to read all keyspaces. TZ> I think the best way to solve this is with an IAuthenticator change to TZ> distinguish between full permissions and read-only permissions. Then TZ> the Thrift API has to be modified to check for write access in only some TZ> functions: ... TZ> Does this seem reasonable? Any comments, while we're discussing authentication? I think read-only access makes a lot of sense in this context. Ted