ninja remove commitlog_periodic_queue_size from cassandra.yaml, and @Deprecate in Config.java

This commit is contained in:
Benedict Elliott Smith 2015-01-28 22:44:35 +00:00
parent 97c54c50c9
commit 160cbc1276
2 changed files with 4 additions and 6 deletions

View File

@ -236,13 +236,9 @@ counter_cache_save_period: 7200
#
# the other option is "periodic" where writes may be acked immediately
# and the CommitLog is simply synced every commitlog_sync_period_in_ms
# milliseconds. commitlog_periodic_queue_size allows 1024*(CPU cores) pending
# entries on the commitlog queue by default. If you are writing very large
# blobs, you should reduce that; 16*cores works reasonably well for 1MB blobs.
# It should be at least as large as the concurrent_writes setting.
# milliseconds.
commitlog_sync: periodic
commitlog_sync_period_in_ms: 10000
# commitlog_periodic_queue_size:
# The size of the individual commitlog file segments. A commitlog
# segment may be archived, deleted, or recycled once all the data

View File

@ -153,7 +153,9 @@ public class Config
public Double commitlog_sync_batch_window_in_ms;
public Integer commitlog_sync_period_in_ms;
public int commitlog_segment_size_in_mb = 32;
public int commitlog_periodic_queue_size = 1024 * FBUtilities.getAvailableProcessors();
@Deprecated
public int commitlog_periodic_queue_size = -1;
public String endpoint_snitch;
public Boolean dynamic_snitch = true;