The question is more from a multi-tenancy point of view. We wanted to see if we can have a keyspace per client. Each keyspace may have 50 column families, but if we have 200 clients, that would be 10,000 column families. Do you think that's reasonable to support? I know that key cache capacity is reserved in heap still. Any plans to move it off-heap?
-Raj On Tue, Nov 25, 2014 at 3:10 PM, Robert Coli <rc...@eventbrite.com> wrote: > On Tue, Nov 25, 2014 at 9:07 AM, Raj N <raj.cassan...@gmail.com> wrote: > >> What's the latest on the maximum number of keyspaces and/or tables that >> one can have in Cassandra 2.1.x? >> > > Most relevant changes lately would be : > > https://issues.apache.org/jira/browse/CASSANDRA-6689 > and > https://issues.apache.org/jira/browse/CASSANDRA-6694 > > Which should meaningfully reduce the amount of heap memtables consume. > That heap can then be used to support more heap-persistent structures > associated with many CFs. I have no idea how to estimate the scale of the > improvement. > > As a general/meta statement, Cassandra is very multi-threaded, and > consumes file handles like crazy. How many different query cases do you > really want to put on one cluster/node? ;D > > =Rob > >
