Re: Reasonable range for the max number of tables?

Hi Mark, Mark Reddy wrote > To segregate customer data, you could: > - Use customer specific column families under a single keyspace > - Use a keyspace per customer These effectively amount to the same thing and they both fall foul to the limit in the number of column families so do not scale.

Re: Reasonable range for the max number of tables?

Is there any mention of this limitation anywhere in the Cassandra documentation? I don't see it mentioned in the 'Anti-patterns in Cassandra' section of the DataStax 2.0 documentation or anywhere else. When starting out with Cassandra as a store for a multi-tenant application it seems very attract

Re: RPC timeout paging secondary index query results

Ken Hancock wrote > You didn't post any timings, only when it started failing so it's unclear > whether performance is dropping off or scaling in some sort of linear or > non-linear fashion. Second the recommendation to do some traces which > should be much more telling. I'm afraid I've not yet ha

Re: RPC timeout paging secondary index query results

But would you expect performance to drop off so quickly? At 250,000 records we can still page through the query with LIMIT 5 but when adding an additional 50,000 records we can't page past the first 10,000 records even if we drop to LIMIT 10. What about the case where we add 100,000 records fo

Re: RPC timeout paging secondary index query results

The problem appears to be directly related to number of entries in the index. I started with an empty table and added 50,000 entries at a time with the same indexed value. I was able to page through the results of a query that used the secondary index with 250,000 records in the table using a LIMIT

Re: RPC timeout paging secondary index query results

Thanks Rob. I understand that we will probably end up either creating our own index or duplicating the data and we have done that to remove a reliance on secondary indexes in other places. It just seems that what we are trying to do here is such basic functionality of an index that I thought we mu

RPC timeout paging secondary index query results

Is paging through the results of a secondary index query broken in Cassandra 2.0.7 or are we doing something wrong? We have table with a few hundred thousand records and an indexed low-cardinality column. The relevant bits of the table definition are shown below CREATE TABLE measurement ( measure

Re: Change number of vnodes on an existing cluster

Thank you Rob, that's all really useful information. As our production cluster is going to grow over time it looks like we may need to stick with vnodes (but maybe not 256) and as you say hope the work to improve their inefficiencies progresses quite quickly. > In real reality, vnodes were almost

RE: Can SSTables overlap with SizeTieredCompactionStrategy?

d rate. Please check. > > > Kind regards > > Andreas Finke > Java Developer > Solvians IT-Solutions GmbH > > > Phil Luckhurst wrote > > Definitely no TTL and records are only written once with no deletions. > > Phil > > > Duy

Re: Change number of vnodes on an existing cluster

fault yaml file. For a small cluster, e.g. 9 nodes with RF=3 would you actually recommend using vnodes at all and if so how many? Phil Robert Coli-3 wrote > On Thu, May 22, 2014 at 4:31 AM, Phil Luckhurst < > phil.luckhurst@ >> wrote: > >> We have a 3 node 2.0.7 cluster

Change number of vnodes on an existing cluster

We have a 3 node 2.0.7 cluster with RF=3. At the moment these are configured to have the default 256 vnodes we'd like to try reducing that to see what effect it has on some of our CQL query times. It seems from CASSANDRA-7057 that there is

RE: Can SSTables overlap with SizeTieredCompactionStrategy?

Definitely no TTL and records are only written once with no deletions. Phil DuyHai Doan wrote > Are you sure there is no TTL set on your data? It might explain the shrink > in sstable size after compaction. -- View this message in context: http://cassandra-user-incubator-apache-org.3065146

RE: Can SSTables overlap with SizeTieredCompactionStrategy?

We based the estimate on a previous controlled observation. We generated a year's worth of one minute data for a single identifier and recorded the size of the resulting sstable. By adding the data one month at a time we observed that there was a linear predictable increase in the sstable size. Usi

Re: Can SSTables overlap with SizeTieredCompactionStrategy?

I'm wondering if the lack of response to this means it was a dumb question however I've searched the documentation again but I still can't find an answer :-( Phil -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Can-SSTables-overlap-with-SizeTie

Can SSTables overlap with SizeTieredCompactionStrategy?

We have a table defined using SizeTieredCompactionStrategy that is used to store time series data. Over a period of a few days we wrote approximately 200,000 unique time based entries for each of 700 identifiers, i.e. 700 wide rows with 200,000 entries in each. The table was empty when we started

Re: binary protocol server side sockets

p://www.blackbirdit.com/>; > > *"Formerly PalominoDB/DriveDev"* > > > On Fri, Apr 11, 2014 at 3:04 AM, Phil Luckhurst < > phil.luckhurst@ >> wrote: > >> We are also seeing this in our development environment. We have a 3 node >> Cassan

Re: binary protocol server side sockets

We are also seeing this in our development environment. We have a 3 node Cassandra 2.0.5 cluster running on Ubuntu 12.04 and are connecting from a Tomcat based application running on Windows using the 2.0.0 Cassandra Java Driver. We have setKeepAlive(true) when building the cluster in the applicati

Re: Gossip intermittently marks node as DOWN

I think we've found the issue! It seems that the times on those Cassandra servers was being kept in sync by vmware tools using the time of the vmware host machine. We have now turned that off and are using the ntp service to keep the times in sync like we do for our physical servers and we have no

Re: Gossip intermittently marks node as DOWN

Here's the tpstats output from both nodes. Johnny Miller wrote > What is nodetool tpstats telling you? -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Gossip-intermittently-marks-node-as-DOWN-tp7593189p7593206.html Sent from the cassandr

Re: Gossip intermittently marks node as DOWN

It was created with the default settings so we have 256 per node. Fabrice Facorat wrote > From what I understand, this can happen when having many nodes and > vnodes by node. How many vnodes did you configure on your nodes ? > > 2014-03-04 11:37 GMT+01:00 Phil Luckhurst < &

RE: Gossip intermittently marks node as DOWN

The VMs are hosted on the same ESXi server and they are just running Cassandra. We seem to get this happen even if the nodes appear to be idle; about 2 to 4 times per hour. Phil -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Gossip-interm

Re: Invalid compacted_at timestamp entries in Cassandra 2.0.5

Thanks. -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Invalid-compacted-at-timestamp-entries-in-Cassandra-2-0-5-tp7593190p7593192.html Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.

Invalid compacted_at timestamp entries in Cassandra 2.0.5

Running 'nodetool compactionHistory' seems to be showing strange timestamp values for the 'compacted_at' column. e.g. id keyspace_name columnfamily_namecompacted_at bytes_in bytes_out rows_merged cb035320-

Gossip intermittently marks node as DOWN

We have a 2 node Cassandra 2.0.5 cluster running on a couple of VMWare hosted virtual machines using Ubuntu 12.04 for testing. As you can see from the log entries below the gossip connection between the nodes regularly goes DOWN and UP. We saw on another post that increasing the phi_convict_thresho