You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by br...@apache.org on 2011/03/12 00:55:08 UTC

svn commit: r1080806 - /cassandra/branches/cassandra-0.7/conf/cassandra.yaml

Author: brandonwilliams
Date: Fri Mar 11 23:55:08 2011
New Revision: 1080806

URL: http://svn.apache.org/viewvc?rev=1080806&view=rev
Log:
Remove binary_memtable_throughput_in_mb from yaml to avoid confusion

Modified:
    cassandra/branches/cassandra-0.7/conf/cassandra.yaml

Modified: cassandra/branches/cassandra-0.7/conf/cassandra.yaml
URL: http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.7/conf/cassandra.yaml?rev=1080806&r1=1080805&r2=1080806&view=diff
==============================================================================
--- cassandra/branches/cassandra-0.7/conf/cassandra.yaml (original)
+++ cassandra/branches/cassandra-0.7/conf/cassandra.yaml Fri Mar 11 23:55:08 2011
@@ -228,10 +228,6 @@ snapshot_before_compaction: false
 # lowest priority and that is our default.
 # compaction_thread_priority: 1
 
-# The threshold size in megabytes the binary memtable must grow to,
-# before it's submitted for flushing to disk.
-binary_memtable_throughput_in_mb: 256
-
 # Add column indexes to a row after its contents reach this size.
 # Increase if your column values are large, or if you have a very large
 # number of columns.  The competing causes are, Cassandra has to