Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of mailtokamal@gmail.com
 designates 209.85.214.172 as permitted sender)
MIME-Version: 1.0
From: Kamal Bahadur <mailtokamal@gmail.com>
Date: Wed, 18 Jan 2012 09:53:22 -0800
Message-ID: 
 <CALoDn7tnSonW3NA_WJBSHSa8CqLC=L534KpLeV+Mw8JqpabBFA@mail.gmail.com>
Subject: Max records per node for a given secondary index value
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=e89a8f234325e67a4b04b6d12078

--e89a8f234325e67a4b04b6d12078
Content-Type: text/plain; charset=UTF-8

Hi All,

It is great to know that Cassandra column family can accommodate 2 billion
columns per row! I was reading about how Cassandra stores the secondary
index info internally. I now understand that the index related data are
stored in hidden CF and each node is responsible to store the keys of data
that reside on that node only.

I have been using secondary index for a low cardinality column called
"product". There can only be 3 possible values for this column. I have a
four node cluster and process about 5000 records per second with a RF 2.

My question here is, what happens after the number of columns in hidden
index CF exceeds 2 billion? How does Cassandra handle this situation? I
guess, one way to handle this is to add more nodes to the cluster. I am
interested in knowing if any other solution exist.

Thanks,
Kamal

--e89a8f234325e67a4b04b6d12078
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi All,<br><br>It is great to know that Cassandra column family can accommo=
date 2 billion columns per row! I was reading about how Cassandra stores th=
e secondary index info internally. I now understand that the index related =
data are stored in hidden CF and each node is responsible to store the keys=
 of data that reside on that node only. <br>

<br>I have been using secondary index for a low cardinality column called &=
quot;product&quot;. There can only be 3 possible values for this column. I =
have a four node cluster and process about 5000 records per second with a R=
F 2.<br>

<br>My question here is, what happens after the number of columns in hidden=
 index CF exceeds 2 billion? How does Cassandra handle this situation? I gu=
ess, one way to handle this is to add more nodes to the cluster. I am inter=
ested in knowing if any other solution exist.<br>

<br>Thanks,<br>Kamal<br>

--e89a8f234325e67a4b04b6d12078--