From 1c12d7bd9c7ef6e7a56c8e4ac8e82fd11e40e868 Mon Sep 17 00:00:00 2001 From: Brandon Williams Date: Fri, 11 Mar 2011 23:55:08 +0000 Subject: [PATCH] Remove binary_memtable_throughput_in_mb from yaml to avoid confusion git-svn-id: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@1080806 13f79535-47bb-0310-9956-ffa450edef68 --- conf/cassandra.yaml | 4 ---- 1 file changed, 4 deletions(-) diff --git a/conf/cassandra.yaml b/conf/cassandra.yaml index 4125f6584f..95884f1675 100644 --- a/conf/cassandra.yaml +++ b/conf/cassandra.yaml @@ -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