Each node is stores the rows in it's token range, and those in the token
ranges it is a replica for. So it will store roughly num_nodes / rf the rows.
If you are approaching a situation where the node may store 2 billion rows, and
so may have 2 billion entries in the secondary index row, you
You need to shard your rows
On Wed, Jan 18, 2012 at 5:46 PM, Kamal Bahadur wrote:
> Anyone?
>
>
> On Wed, Jan 18, 2012 at 9:53 AM, Kamal Bahadur
> wrote:
>>
>> Hi All,
>>
>> It is great to know that Cassandra column family can accommodate 2 billion
>> columns per row! I was reading about how Cas
Anyone?
On Wed, Jan 18, 2012 at 9:53 AM, Kamal Bahadur wrote:
> 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 ar
