We only have a single CF per keyspace. Actually we have 2, but one is tiny
(only has 2 rows in it and is queried once a month or less).
Yup, using vnodes with 256 tokens.
Cassandra 1.2.10.
-- C
On Mon, Nov 25, 2013 at 2:28 PM, John Pyeatt wrote:
> Mr. Bottaro,
>
> About how many column famil
On Mon, Nov 25, 2013 at 12:28 PM, John Pyeatt wrote:
> Are you using Vnodes? We are and they are set to 256
> What version of cassandra are you running. We are running 1.2.9
>
Vnode performance vis a vis repair is this JIRA issue :
https://issues.apache.org/jira/browse/CASSANDRA-5220
Unfortunat
Mr. Bottaro,
About how many column families are in your keyspaces? We have 28 per
keyspace.
Are you using Vnodes? We are and they are set to 256
What version of cassandra are you running. We are running 1.2.9
On Mon, Nov 25, 2013 at 11:36 AM, Christopher J. Bottaro <
cjbott...@academicworks.co
We have the same setup: one keyspace per client, and currently about 300
keyspaces. nodetool repair takes a long time, 4 hours with -pr on a single
node. We have a 4 node cluster with about 10 gb per node. Unfortunately,
we haven't been keeping track of the running time as keyspaces, or load,
i
We have an application that has been designed to use potentially 100s of
keyspaces (one for each company).
One thing we are noticing is that nodetool repair across all of the
keyspaces seems to increase linearly based on the number of keyspaces. For
example, if we have a 6 node ec2 (m1.large) clus
