[
https://issues.apache.org/jira/browse/CASSANDRA-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984118#action_12984118
]
David Boxenhorn commented on CASSANDRA-2006:
--------------------------------------------
The way I see it - and it becomes even more necessary for a multi-tenant
configuration - there should be three completely separate levels of
configuration.
- Column family configuration is based on data and usage characteristics of
column families in your application.
- Keyspace configuration enables the modularization of your application (and in
a multi-tenant environment, you can assign a keyspace to a tenant)
- Server configuration is based on the specific hardware limitations of the
server.
Server configuration takes priority over keyspace configuration which takes
priority over application configuration.
Looking at if from the inverse perspective:
- CF configuration tunes access to your CFs
- Keyspace configuration protects one module of your application from problems
in the other modules
- Server configuration protects the server as a whole from going beyond the
limits of its hardware
> Serverwide caps on memtable thresholds
> --------------------------------------
>
> Key: CASSANDRA-2006
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2006
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Stu Hood
> Fix For: 0.8
>
>
> By storing global operation and throughput thresholds, we could eliminate the
> "many small memtables" problem caused by having many CFs. The global
> threshold would be set in the config file, to allow different classes of
> servers to have different values configured.
> Operations occurring in the memtable would add to the global counters, in
> addition to the memtable-local counters. When a global threshold was
> violated, the memtable in the system that was using the largest fraction of
> it's local threshold would be flushed. Local thresholds would continue to act
> as they always have.
> The result would be larger sstables, safer operation with multiple CFs and
> per node tuning.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
