Remove unused max_value_size_in_mb config setting

Fixes #124

Patch by Joaquin Casares; Reviewed by Jeff Jirsa for CASSANDRA-13625
This commit is contained in:
Joaquin Casares 2017-06-20 18:26:26 -05:00 committed by Jeff Jirsa
parent 83f28ce3c4
commit 082af0a9ba
2 changed files with 4 additions and 5 deletions

View File

@ -1,3 +1,7 @@
2.2.11
* Remove unused max_value_size_in_mb config setting from yaml (CASSANDRA-13625
2.2.10
* Nodes started with join_ring=False should be able to serve requests when authentication is enabled (CASSANDRA-11381)
* cqlsh COPY FROM: increment error count only for failures, not for attempts (CASSANDRA-13209)

View File

@ -885,11 +885,6 @@ enable_user_defined_functions: false
# setting.
windows_timer_interval: 1
# Maximum size of any value in SSTables. Safety measure to detect SSTable corruption
# early. Any value size larger than this threshold will result into marking an SSTable
# as corrupted.
# max_value_size_in_mb: 256
# Coalescing Strategies #
# Coalescing multiples messages turns out to significantly boost message processing throughput (think doubling or more).
# On bare metal, the floor for packet processing throughput is high enough that many applications won't notice, but in