incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: Cassandra CF sharding
Date Fri, 28 May 2010 03:11:10 GMT
2) is correct, but for 1) I'm not sure what manageability improvements
you anticipate from dealing with multiple entities instead of one.
I'm not sure what you're thinking of for 3) but routing is done by key
only.

2010/5/27 Maxim Kramarenko <maximkr@trackstudio.com>:
> Hello!
>
> We have mail archive with one large CF for mail body. In our case, it's easy
> to shard data to 5-10 CF by customer id. We like to do this because:
>
> 1) We get more manageable instances, because we have many small CF instead
> of one multi-TB CF on each node.
>
> 2) Better disk space usage (need to reserve 50% of the largest shard for
> compaction only)
>
> 3) Can manage node load not by token only, but also by defining shards
> available per node.
>
> Is my assumptions correct ? Any negative side effects ?
>



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com

Mime
View raw message