Dear Wiki user, You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.
The "MultiTenant" page has been changed by jeremyhanna. http://wiki.apache.org/cassandra/MultiTenant?action=diff&rev1=7&rev2=8 -------------------------------------------------- * Basic scheduling based on keyspace - [[https://issues.apache.org/jira/browse/CASSANDRA-1035|CASSANDRA-1035]] * Better authorization system - [[https://issues.apache.org/jira/browse/CASSANDRA-1237|CASSANDRA-1237]], [[https://issues.apache.org/jira/browse/CASSANDRA-1271|CASSANDRA-1271]] * Concurrent schema migrations (multiple users changing schema at once) - [[https://issues.apache.org/jira/browse/CASSANDRA-1391|CASSANDRA-1391]] + * For multi-tenant order preserved partitioning, auto/online load balancing is pretty important [[https://issues.apache.org/jira/browse/CASSANDRA-1418|CASSANDRA-1418]] == Ideas under consideration == * Implement a weighted scheduler - e.g. for dev/prod accounts on the same cluster * Provide relative memory usage settings for caches and Memtables out of configurable (per-user?) totals + * Namespaces - in a multi-tenant use case, each user might like to have a keyspace XYZ for whatever reason. So it might be nice to have namespaces so that keyspace XYZ could be specific to their user. Ideally this would be an option that would not affect those that don't use namespaces. + * JMX authentication without breaking nodetool - currently if you try to use JMX authentication, some of the Cassandra tools won't connect properly. * Perhaps provide a way to throttle certain operations, maybe useful outside the scope of multi-tenancy. Voldemort, for example, uses a [[http://github.com/voldemort/voldemort/blob/master/src/java/voldemort/utils/EventThrottler.java|throttler]] for operations that quickly iterate over all the data of a node, such as a rebalance.
