You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2011/01/26 03:24:44 UTC
[jira] Resolved: (CASSANDRA-2043) remove memtable throughput
configuration
[ https://issues.apache.org/jira/browse/CASSANDRA-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-2043.
---------------------------------------
Resolution: Won't Fix
Assignee: (was: Jon Hermes)
having the two settings is still useful for CFs with high variance in column value sizes.
> remove memtable throughput configuration
> ----------------------------------------
>
> Key: CASSANDRA-2043
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2043
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Fix For: 0.8
>
>
> Now that we can set memtable thresholds on a per-CF basis, having two sizing thresholds is more confusing than helpful, especially for new users who see the throughput threshold and think that it accurately represents how much memory a memtable will use
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.