Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B597DD22B for ; Thu, 8 Nov 2012 23:18:18 +0000 (UTC) Received: (qmail 83198 invoked by uid 500); 8 Nov 2012 23:18:16 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 83176 invoked by uid 500); 8 Nov 2012 23:18:16 -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 83167 invoked by uid 99); 8 Nov 2012 23:18:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Nov 2012 23:18:16 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kohlisankalp@gmail.com designates 209.85.216.51 as permitted sender) Received: from [209.85.216.51] (HELO mail-qa0-f51.google.com) (209.85.216.51) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Nov 2012 23:18:08 +0000 Received: by mail-qa0-f51.google.com with SMTP id t11so27176qaa.10 for ; Thu, 08 Nov 2012 15:17:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=o1fmpQNmZZYNRaE/sxEAScElFf7QdnKum4EIfM+wG2I=; b=JuMm5h/5zWMvQDu9SDBCE/u3DsUU+MltiQ4LjFvTgA9/R0uPwefBPEedIK2KKSMAPc Ei8n7erVHpjWnU5NwUaolQZ2+6v2L4aTclVwuvML9NjrJ23hjR8LtMcwDtByqKOZbbTS U9xG74/M50YJw6lldW8gYtyLmlLJpvHop87cCF/q9Ww3PHuHEEoOV1sm5Vkdz7OKDRp9 U+vmTOsZcMg88cYTbb4iKmhIwzbDNwoYt4RhhBsRitJ38B4iVDXpmsYYtm2Vx+z3M1WC re1g0iWHzo9BYQH1ZHlKl5JHp2g/QJe5e8KT7f2nhPTlZAYvD/Lv1sM3wEF/DxHIAUet yrRQ== Received: by 10.224.116.12 with SMTP id k12mr14404009qaq.47.1352416666108; Thu, 08 Nov 2012 15:17:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.49.96.168 with HTTP; Thu, 8 Nov 2012 15:17:25 -0800 (PST) In-Reply-To: References: From: sankalp kohli Date: Thu, 8 Nov 2012 15:17:25 -0800 Message-ID: Subject: Re: Multiple keyspaces vs Multiple CFs To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=20cf3074d7e0f8c1d604ce040aab X-Virus-Checked: Checked by ClamAV on apache.org --20cf3074d7e0f8c1d604ce040aab Content-Type: text/plain; charset=ISO-8859-1 I am a bit confused. One connection pool I know is the one which MessageService has to other nodes. Then there will be incoming connections via thrift from clients. How are they affected by multiple keyspaces? On Thu, Nov 8, 2012 at 3:14 PM, Edward Capriolo wrote: > Any connection pool. Imagine if you have 10 column families in 10 > keyspaces. You pull a connection off the pool and the odds are 1 in 10 > of it being connected to the keyspace you want. So 9 out of 10 times > you have to have a network round trip just to change the keyspace, or > you have to build a keyspace aware connection pool. > Edward > > On Thu, Nov 8, 2012 at 5:36 PM, sankalp kohli > wrote: > > Which connection pool are you talking about? > > > > > > On Thu, Nov 8, 2012 at 2:19 PM, Edward Capriolo > > wrote: > >> > >> it is better to have one keyspace unless you need to replicate the > >> keyspaces differently. The main reason for this is that changing > >> keyspaces requires an RPC operation. Having 10 keyspaces would mean > >> having 10 connection pools. > >> > >> On Thu, Nov 8, 2012 at 4:59 PM, sankalp kohli > >> wrote: > >> > Is it better to have 10 Keyspaces with 10 CF in each keyspace. or 100 > >> > keyspaces with 1 CF each. > >> > I am talking in terms of memory footprint. > >> > Also I would be interested to know how much better one is over other. > >> > > >> > Thanks, > >> > Sankalp > > > > > --20cf3074d7e0f8c1d604ce040aab Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I am a bit confused. One connection pool I know is the one which MessageSer= vice has to other nodes. Then there will be incoming connections via thrift= from clients. How are they affected by multiple keyspaces?


On Thu, Nov 8, 2012 at 3:14 PM, Edward C= apriolo <edlinuxguru@gmail.com> wrote:
Any connection pool. Imagine if you have 10 column families in 10
keyspaces. You pull a connection off the pool and the odds are 1 in 10
of it being connected to the keyspace you want. So 9 out of 10 times
you have to have a network round trip just to change the keyspace, or
you have to build a keyspace aware connection pool.
Edward

On Thu, Nov 8, 2012 at 5:36 PM, sankalp kohli <kohlisankalp@gmail.com> wrote:
> Which connection pool are you talking about?
>
>
> On Thu, Nov 8, 2012 at 2:19 PM, Edward Capriolo <edlinuxguru@gmail.com>
> wrote:
>>
>> it is better to have one keyspace unless you need to replicate the=
>> keyspaces differently. The main reason for this is that changing >> keyspaces requires an RPC operation. Having 10 keyspaces would mea= n
>> having 10 connection pools.
>>
>> On Thu, Nov 8, 2012 at 4:59 PM, sankalp kohli <kohlisankalp@gmail.com>
>> wrote:
>> > Is it better to have 10 Keyspaces with 10 CF in each keyspace= . or 100
>> > keyspaces with 1 CF each.
>> > I am talking in terms of memory footprint.
>> > Also I would be interested to know how much better one is ove= r other.
>> >
>> > Thanks,
>> > Sankalp
>
>

--20cf3074d7e0f8c1d604ce040aab--