[
https://issues.apache.org/jira/browse/CASSANDRA-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-3246.
---------------------------------------
Resolution: Fixed
Fix Version/s: 1.0.0
Assignee: Jonathan Ellis
The old thresholds were made no-ops in CASSANDRA-2449. I removed the line "If
set to 0, only the old flush thresholds are used" just now in r1174563.
> memtable_total_space_in_mb does not accept the value 0 in Cassandra 1.0
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-3246
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3246
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.0
> Reporter: Tyler Hobbs
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 1.0.0
>
>
> This affects 1.0 beta1.
> From the key explanation in cassandra.yaml it looks like it should accept the
> value "0"
> # Total memory to use for memtables. Cassandra will flush the largest
> # memtable when this much memory is used.
> # If omitted, Cassandra will set it to 1/3 of the heap.
> # If set to 0, only the old flush thresholds are used.
> memtable_total_space_in_mb: 0
> However in the code I could see the following:
> if (conf.memtable_total_space_in_mb <= 0)
> throw new ConfigurationException("memtable_total_space_in_mb must be
> positive");
> logger.info("Global memtable threshold is enabled at {}MB",
> conf.memtable_total_space_in_mb);
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
