-user-incubator-apache-org.3065146.n2.nabble.com/Cassandra-CF-sharding-tp5110445p5655818.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
Hello!
Thank you.
In 1) I hope, that processing smaller files will be more easy to
monitor. Also, if we have disk failure, we can delete just one file and
repair, for example. Actually, CF per customer will be the best (easy to
delete/backup specified customer data only, customers are totally
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 :
> Hello!
>
> We have mail archive with one large CF fo
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 (ne
