Update cassandra.yaml documentation for batch_size thresholds

Take account of changes in CASSANDRA-10876

Patch by Guy Bolton King; reviewed by Joel Knighton for CASSANDRA-12761
This commit is contained in:
Guy Bolton King 2016-09-20 14:55:24 +01:00 committed by Aleksey Yeschenko
parent 206a7bbac7
commit e722046406
2 changed files with 3 additions and 2 deletions

View File

@ -1,4 +1,5 @@
3.10
* Make cassandra.yaml docs for batch_size_*_threshold_in_kb reflect changes in CASSANDRA-10876 (CASSANDRA-12761)
* cqlsh fails to format collections when using aliases (CASSANDRA-11534)
* Check for hash conflicts in prepared statements (CASSANDRA-12733)
* Exit query parsing upon first error (CASSANDRA-12598)

View File

@ -1150,11 +1150,11 @@ transparent_data_encryption_options:
tombstone_warn_threshold: 1000
tombstone_failure_threshold: 100000
# Log WARN on any batch size exceeding this value. 5kb per batch by default.
# Log WARN on any multiple-partition batch size exceeding this value. 5kb per batch by default.
# Caution should be taken on increasing the size of this threshold as it can lead to node instability.
batch_size_warn_threshold_in_kb: 5
# Fail any batch exceeding this value. 50kb (10x warn threshold) by default.
# Fail any multiple-partition batch exceeding this value. 50kb (10x warn threshold) by default.
batch_size_fail_threshold_in_kb: 50
# Log WARN on any batches not of type LOGGED than span across more partitions than this limit