Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- # Cassandra storage config YAML
- 2
- 3 # NOTE:
- 4 # See http://wiki.apache.org/cassandra/StorageConfiguration for
- 5 # full explanations of configuration directives
- 6 # /NOTE
- 7
- 8 # The name of the cluster. This is mainly used to prevent machines in
- 9 # one logical cluster from joining another.
- 10 cluster_name: 'Test Cluster'
- 11
- 12 # This defines the number of tokens randomly assigned to this node on the ring
- 13 # The more tokens, relative to other nodes, the larger the proportion of data
- 14 # that this node will store. You probably want all nodes to have the same number
- 15 # of tokens assuming they have equal hardware capability.
- 16 #
- 17 # If you leave this unspecified, Cassandra will use the default of 1 token for legacy compatibility,
- 18 # and will use the initial_token as described below.
- 19 #
- 20 # Specifying initial_token will override this setting on the node's initial start,
- 21 # on subsequent starts, this setting will apply even if initial token is set.
- 22 #
- 23 # If you already have a cluster with 1 token per node, and wish to migrate to
- 24 # multiple tokens per node, see http://wiki.apache.org/cassandra/Operations
- 25 num_tokens: 256
- 26
- 27 # Triggers automatic allocation of num_tokens tokens for this node. The allocation
- 28 # algorithm attempts to choose tokens in a way that optimizes replicated load over
- 29 # the nodes in the datacenter for the replication strategy used by the specified
- 30 # keyspace.
- 31 #
- 32 # The load assigned to each node will be close to proportional to its number of
- 33 # vnodes.
- 34 #
- 35 # Only supported with the Murmur3Partitioner.
- 36 # allocate_tokens_for_keyspace: KEYSPACE
- 37
- 38 # initial_token allows you to specify tokens manually. While you can use it with
- 39 # vnodes (num_tokens > 1, above) -- in which case you should provide a
- 40 # comma-separated list -- it's primarily used when adding nodes to legacy clusters
- 41 # that do not have vnodes enabled.
- 42 # initial_token:
- 43
- 44 # See http://wiki.apache.org/cassandra/HintedHandoff
- 45 # May either be "true" or "false" to enable globally
- 46 hinted_handoff_enabled: true
- 47
- 48 # When hinted_handoff_enabled is true, a black list of data centers that will not
- 49 # perform hinted handoff
- 50 # hinted_handoff_disabled_datacenters:
- 51 # - DC1
- 52 # - DC2
- 53
- 54 # this defines the maximum amount of time a dead host will have hints
- 55 # generated. After it has been dead this long, new hints for it will not be
- 56 # created until it has been seen alive and gone down again.
- 57 max_hint_window_in_ms: 10800000 # 3 hours
- 58
- 59 # Maximum throttle in KBs per second, per delivery thread. This will be
- 60 # reduced proportionally to the number of nodes in the cluster. (If there
- 61 # are two nodes in the cluster, each delivery thread will use the maximum
- 62 # rate; if there are three, each will throttle to half of the maximum,
- 63 # since we expect two nodes to be delivering hints simultaneously.)
- 64 hinted_handoff_throttle_in_kb: 1024
- 65
- 66 # Number of threads with which to deliver hints;
- 67 # Consider increasing this number when you have multi-dc deployments, since
- 68 # cross-dc handoff tends to be slower
- 69 max_hints_delivery_threads: 2
- 70
- 71 # Directory where Cassandra should store hints.
- 72 # If not set, the default directory is $CASSANDRA_HOME/data/hints.
- 73 # hints_directory: /var/lib/cassandra/hints
- 74
- 75 # How often hints should be flushed from the internal buffers to disk.
- 76 # Will *not* trigger fsync.
- 77 hints_flush_period_in_ms: 10000
- 78
- 79 # Maximum size for a single hints file, in megabytes.
- 80 max_hints_file_size_in_mb: 128
- 81
- 82 # Compression to apply to the hint files. If omitted, hints files
- 83 # will be written uncompressed. LZ4, Snappy, and Deflate compressors
- 84 # are supported.
- 85 #hints_compression:
- 86 # - class_name: LZ4Compressor
- 87 # parameters:
- 88 # -
- 89
- 90 # Maximum throttle in KBs per second, total. This will be
- 91 # reduced proportionally to the number of nodes in the cluster.
- 92 batchlog_replay_throttle_in_kb: 1024
- 93
- 94 # Authentication backend, implementing IAuthenticator; used to identify users
- 95 # Out of the box, Cassandra provides org.apache.cassandra.auth.{AllowAllAuthenticator,
- 96 # PasswordAuthenticator}.
- 97 #
- 98 # - AllowAllAuthenticator performs no checks - set it to disable authentication.
- 99 # - PasswordAuthenticator relies on username/password pairs to authenticate
- 100 # users. It keeps usernames and hashed passwords in system_auth.credentials table.
- 101 # Please increase system_auth keyspace replication factor if you use this authenticator.
- 102 # If using PasswordAuthenticator, CassandraRoleManager must also be used (see below)
- 103 authenticator: AllowAllAuthenticator
- 104
- 105 # Authorization backend, implementing IAuthorizer; used to limit access/provide permissions
- 106 # Out of the box, Cassandra provides org.apache.cassandra.auth.{AllowAllAuthorizer,
- 107 # CassandraAuthorizer}.
- 108 #
- 109 # - AllowAllAuthorizer allows any action to any user - set it to disable authorization.
- 110 # - CassandraAuthorizer stores permissions in system_auth.permissions table. Please
- 111 # increase system_auth keyspace replication factor if you use this authorizer.
- 112 authorizer: AllowAllAuthorizer
- 113
- 114 # Part of the Authentication & Authorization backend, implementing IRoleManager; used
- 115 # to maintain grants and memberships between roles.
- 116 # Out of the box, Cassandra provides org.apache.cassandra.auth.CassandraRoleManager,
- 117 # which stores role information in the system_auth keyspace. Most functions of the
- 118 # IRoleManager require an authenticated login, so unless the configured IAuthenticator
- 119 # actually implements authentication, most of this functionality will be unavailable.
- 120 #
- 121 # - CassandraRoleManager stores role data in the system_auth keyspace. Please
- 122 # increase system_auth keyspace replication factor if you use this role manager.
- 123 role_manager: CassandraRoleManager
- 124
- 125 # Validity period for roles cache (fetching granted roles can be an expensive
- 126 # operation depending on the role manager, CassandraRoleManager is one example)
- 127 # Granted roles are cached for authenticated sessions in AuthenticatedUser and
- 128 # after the period specified here, become eligible for (async) reload.
- 129 # Defaults to 2000, set to 0 to disable caching entirely.
- 130 # Will be disabled automatically for AllowAllAuthenticator.
- 131 roles_validity_in_ms: 2000
- 132
- 133 # Refresh interval for roles cache (if enabled).
- 134 # After this interval, cache entries become eligible for refresh. Upon next
- 135 # access, an async reload is scheduled and the old value returned until it
- 136 # completes. If roles_validity_in_ms is non-zero, then this must be
- 137 # also.
- 138 # Defaults to the same value as roles_validity_in_ms.
- 139 # roles_update_interval_in_ms: 2000
- 140
- 141 # Validity period for permissions cache (fetching permissions can be an
- 142 # expensive operation depending on the authorizer, CassandraAuthorizer is
- 143 # one example). Defaults to 2000, set to 0 to disable.
- 144 # Will be disabled automatically for AllowAllAuthorizer.
- 145 permissions_validity_in_ms: 2000
- 146
- 147 # Refresh interval for permissions cache (if enabled).
- 148 # After this interval, cache entries become eligible for refresh. Upon next
- 149 # access, an async reload is scheduled and the old value returned until it
- 150 # completes. If permissions_validity_in_ms is non-zero, then this must be
- 151 # also.
- 152 # Defaults to the same value as permissions_validity_in_ms.
- 153 # permissions_update_interval_in_ms: 2000
- 154
- 155 # Validity period for credentials cache. This cache is tightly coupled to
- 156 # the provided PasswordAuthenticator implementation of IAuthenticator. If
- 157 # another IAuthenticator implementation is configured, this cache will not
- 158 # be automatically used and so the following settings will have no effect.
- 159 # Please note, credentials are cached in their encrypted form, so while
- 160 # activating this cache may reduce the number of queries made to the
- 161 # underlying table, it may not bring a significant reduction in the
- 162 # latency of individual authentication attempts.
- 163 # Defaults to 2000, set to 0 to disable credentials caching.
- 164 credentials_validity_in_ms: 2000
- 165
- 166 # Refresh interval for credentials cache (if enabled).
- 167 # After this interval, cache entries become eligible for refresh. Upon next
- 168 # access, an async reload is scheduled and the old value returned until it
- 169 # completes. If credentials_validity_in_ms is non-zero, then this must be
- 170 # also.
- 171 # Defaults to the same value as credentials_validity_in_ms.
- 172 # credentials_update_interval_in_ms: 2000
- 173
- 174 # The partitioner is responsible for distributing groups of rows (by
- 175 # partition key) across nodes in the cluster. You should leave this
- 176 # alone for new clusters. The partitioner can NOT be changed without
- 177 # reloading all data, so when upgrading you should set this to the
- 178 # same partitioner you were already using.
- 179 #
- 180 # Besides Murmur3Partitioner, partitioners included for backwards
- 181 # compatibility include RandomPartitioner, ByteOrderedPartitioner, and
- 182 # OrderPreservingPartitioner.
- 183 #
- 184 partitioner: org.apache.cassandra.dht.Murmur3Partitioner
- 185
- 186 # Directories where Cassandra should store data on disk. Cassandra
- 187 # will spread data evenly across them, subject to the granularity of
- 188 # the configured compaction strategy.
- 189 # If not set, the default directory is $CASSANDRA_HOME/data/data.
- 190 # data_file_directories:
- 191 # - /var/lib/cassandra/data
- 192
- 193 # commit log. when running on magnetic HDD, this should be a
- 194 # separate spindle than the data directories.
- 195 # If not set, the default directory is $CASSANDRA_HOME/data/commitlog.
- 196 # commitlog_directory: /var/lib/cassandra/commitlog
- 197
- 198 # Enable / disable CDC functionality on a per-node basis. This modifies the logic used
- 199 # for write path allocation rejection (standard: never reject. cdc: reject Mutation
- 200 # containing a CDC-enabled table if at space limit in cdc_raw_directory).
- 201 cdc_enabled: false
- 202
- 203 # CommitLogSegments are moved to this directory on flush if cdc_enabled: true and the
- 204 # segment contains mutations for a CDC-enabled table. This should be placed on a
- 205 # separate spindle than the data directories. If not set, the default directory is
- 206 # $CASSANDRA_HOME/data/cdc_raw.
- 207 # cdc_raw_directory: /var/lib/cassandra/cdc_raw
- 208
- 209 # Policy for data disk failures:
- 210 #
- 211 # die
- 212 # shut down gossip and client transports and kill the JVM for any fs errors or
- 213 # single-sstable errors, so the node can be replaced.
- 214 #
- 215 # stop_paranoid
- 216 # shut down gossip and client transports even for single-sstable errors,
- 217 # kill the JVM for errors during startup.
- 218 #
- 219 # stop
- 220 # shut down gossip and client transports, leaving the node effectively dead, but
- 221 # can still be inspected via JMX, kill the JVM for errors during startup.
- 222 #
- 223 # best_effort
- 224 # stop using the failed disk and respond to requests based on
- 225 # remaining available sstables. This means you WILL see obsolete
- 226 # data at CL.ONE!
- 227 #
- 228 # ignore
- 229 # ignore fatal errors and let requests fail, as in pre-1.2 Cassandra
- 230 disk_failure_policy: stop
- 231
- 232 # Policy for commit disk failures:
- 233 #
- 234 # die
- 235 # shut down gossip and Thrift and kill the JVM, so the node can be replaced.
- 236 #
- 237 # stop
- 238 # shut down gossip and Thrift, leaving the node effectively dead, but
- 239 # can still be inspected via JMX.
- 240 #
- 241 # stop_commit
- 242 # shutdown the commit log, letting writes collect but
- 243 # continuing to service reads, as in pre-2.0.5 Cassandra
- 244 #
- 245 # ignore
- 246 # ignore fatal errors and let the batches fail
- 247 commit_failure_policy: stop
- 248
- 249 # Maximum size of the native protocol prepared statement cache
- 250 #
- 251 # Valid values are either "auto" (omitting the value) or a value greater 0.
- 252 #
- 253 # Note that specifying a too large value will result in long running GCs and possbily
- 254 # out-of-memory errors. Keep the value at a small fraction of the heap.
- 255 #
- 256 # If you constantly see "prepared statements discarded in the last minute because
- 257 # cache limit reached" messages, the first step is to investigate the root cause
- 258 # of these messages and check whether prepared statements are used correctly -
- 259 # i.e. use bind markers for variable parts.
- 260 #
- 261 # Do only change the default value, if you really have more prepared statements than
- 262 # fit in the cache. In most cases it is not neccessary to change this value.
- 263 # Constantly re-preparing statements is a performance penalty.
- 264 #
- 265 # Default value ("auto") is 1/256th of the heap or 10MB, whichever is greater
- 266 prepared_statements_cache_size_mb:
- 267
- 268 # Maximum size of the Thrift prepared statement cache
- 269 #
- 270 # If you do not use Thrift at all, it is safe to leave this value at "auto".
- 271 #
- 272 # See description of 'prepared_statements_cache_size_mb' above for more information.
- 273 #
- 274 # Default value ("auto") is 1/256th of the heap or 10MB, whichever is greater
- 275 thrift_prepared_statements_cache_size_mb:
- 276
- 277 # Maximum size of the key cache in memory.
- 278 #
- 279 # Each key cache hit saves 1 seek and each row cache hit saves 2 seeks at the
- 280 # minimum, sometimes more. The key cache is fairly tiny for the amount of
- 281 # time it saves, so it's worthwhile to use it at large numbers.
- 282 # The row cache saves even more time, but must contain the entire row,
- 283 # so it is extremely space-intensive. It's best to only use the
- 284 # row cache if you have hot rows or static rows.
- 285 #
- 286 # NOTE: if you reduce the size, you may not get you hottest keys loaded on startup.
- 287 #
- 288 # Default value is empty to make it "auto" (min(5% of Heap (in MB), 100MB)). Set to 0 to disable key cache.
- 289 key_cache_size_in_mb:
- 290
- 291 # Duration in seconds after which Cassandra should
- 292 # save the key cache. Caches are saved to saved_caches_directory as
- 293 # specified in this configuration file.
- 294 #
- 295 # Saved caches greatly improve cold-start speeds, and is relatively cheap in
- 296 # terms of I/O for the key cache. Row cache saving is much more expensive and
- 297 # has limited use.
- 298 #
- 299 # Default is 14400 or 4 hours.
- 300 key_cache_save_period: 14400
- 301
- 302 # Number of keys from the key cache to save
- 303 # Disabled by default, meaning all keys are going to be saved
- 304 # key_cache_keys_to_save: 100
- 305
- 306 # Row cache implementation class name. Available implementations:
- 307 #
- 308 # org.apache.cassandra.cache.OHCProvider
- 309 # Fully off-heap row cache implementation (default).
- 310 #
- 311 # org.apache.cassandra.cache.SerializingCacheProvider
- 312 # This is the row cache implementation availabile
- 313 # in previous releases of Cassandra.
- 314 # row_cache_class_name: org.apache.cassandra.cache.OHCProvider
- 315
- 316 # Maximum size of the row cache in memory.
- 317 # Please note that OHC cache implementation requires some additional off-heap memory to manage
- 318 # the map structures and some in-flight memory during operations before/after cache entries can be
- 319 # accounted against the cache capacity. This overhead is usually small compared to the whole capacity.
- 320 # Do not specify more memory that the system can afford in the worst usual situation and leave some
- 321 # headroom for OS block level cache. Do never allow your system to swap.
- 322 #
- 323 # Default value is 0, to disable row caching.
- 324 row_cache_size_in_mb: 0
- 325
- 326 # Duration in seconds after which Cassandra should save the row cache.
- 327 # Caches are saved to saved_caches_directory as specified in this configuration file.
- 328 #
- 329 # Saved caches greatly improve cold-start speeds, and is relatively cheap in
- 330 # terms of I/O for the key cache. Row cache saving is much more expensive and
- 331 # has limited use.
- 332 #
- 333 # Default is 0 to disable saving the row cache.
- 334 row_cache_save_period: 0
- 335
- 336 # Number of keys from the row cache to save.
- 337 # Specify 0 (which is the default), meaning all keys are going to be saved
- 338 # row_cache_keys_to_save: 100
- 339
- 340 # Maximum size of the counter cache in memory.
- 341 #
- 342 # Counter cache helps to reduce counter locks' contention for hot counter cells.
- 343 # In case of RF = 1 a counter cache hit will cause Cassandra to skip the read before
- 344 # write entirely. With RF > 1 a counter cache hit will still help to reduce the duration
- 345 # of the lock hold, helping with hot counter cell updates, but will not allow skipping
- 346 # the read entirely. Only the local (clock, count) tuple of a counter cell is kept
- 347 # in memory, not the whole counter, so it's relatively cheap.
- 348 #
- 349 # NOTE: if you reduce the size, you may not get you hottest keys loaded on startup.
- 350 #
- 351 # Default value is empty to make it "auto" (min(2.5% of Heap (in MB), 50MB)). Set to 0 to disable counter cache.
- 352 # NOTE: if you perform counter deletes and rely on low gcgs, you should disable the counter cache.
- 353 counter_cache_size_in_mb:
- 354
- 355 # Duration in seconds after which Cassandra should
- 356 # save the counter cache (keys only). Caches are saved to saved_caches_directory as
- 357 # specified in this configuration file.
- 358 #
- 359 # Default is 7200 or 2 hours.
- 360 counter_cache_save_period: 7200
- 361
- 362 # Number of keys from the counter cache to save
- 363 # Disabled by default, meaning all keys are going to be saved
- 364 # counter_cache_keys_to_save: 100
- 365
- 366 # saved caches
- 367 # If not set, the default directory is $CASSANDRA_HOME/data/saved_caches.
- 368 # saved_caches_directory: /var/lib/cassandra/saved_caches
- 369
- 370 # commitlog_sync may be either "periodic" or "batch."
- 371 #
- 372 # When in batch mode, Cassandra won't ack writes until the commit log
- 373 # has been fsynced to disk. It will wait
- 374 # commitlog_sync_batch_window_in_ms milliseconds between fsyncs.
- 375 # This window should be kept short because the writer threads will
- 376 # be unable to do extra work while waiting. (You may need to increase
- 377 # concurrent_writes for the same reason.)
- 378 #
- 379 # commitlog_sync: batch
- 380 # commitlog_sync_batch_window_in_ms: 2
- 381 #
- 382 # the other option is "periodic" where writes may be acked immediately
- 383 # and the CommitLog is simply synced every commitlog_sync_period_in_ms
- 384 # milliseconds.
- 385 commitlog_sync: periodic
- 386 commitlog_sync_period_in_ms: 10000
- 387
- 388 # The size of the individual commitlog file segments. A commitlog
- 389 # segment may be archived, deleted, or recycled once all the data
- 390 # in it (potentially from each columnfamily in the system) has been
- 391 # flushed to sstables.
- 392 #
- 393 # The default size is 32, which is almost always fine, but if you are
- 394 # archiving commitlog segments (see commitlog_archiving.properties),
- 395 # then you probably want a finer granularity of archiving; 8 or 16 MB
- 396 # is reasonable.
- 397 # Max mutation size is also configurable via max_mutation_size_in_kb setting in
- 398 # cassandra.yaml. The default is half the size commitlog_segment_size_in_mb * 1024.
- 399 #
- 400 # NOTE: If max_mutation_size_in_kb is set explicitly then commitlog_segment_size_in_mb must
- 401 # be set to at least twice the size of max_mutation_size_in_kb / 1024
- 402 #
- 403 commitlog_segment_size_in_mb: 32
- 404
- 405 # Compression to apply to the commit log. If omitted, the commit log
- 406 # will be written uncompressed. LZ4, Snappy, and Deflate compressors
- 407 # are supported.
- 408 # commitlog_compression:
- 409 # - class_name: LZ4Compressor
- 410 # parameters:
- 411 # -
- 412
- 413 # any class that implements the SeedProvider interface and has a
- 414 # constructor that takes a Map<String, String> of parameters will do.
- 415 seed_provider:
- 416 # Addresses of hosts that are deemed contact points.
- 417 # Cassandra nodes use this list of hosts to find each other and learn
- 418 # the topology of the ring. You must change this if you are running
- 419 # multiple nodes!
- 420 - class_name: org.apache.cassandra.locator.SimpleSeedProvider
- 421 parameters:
- 422 # seeds is actually a comma-delimited list of addresses.
- 423 # Ex: "<ip1>,<ip2>,<ip3>"
- 424 - seeds: "172.15.81.249,172.15.14.106"
- 425
- 426 # For workloads with more data than can fit in memory, Cassandra's
- 427 # bottleneck will be reads that need to fetch data from
- 428 # disk. "concurrent_reads" should be set to (16 * number_of_drives) in
- 429 # order to allow the operations to enqueue low enough in the stack
- 430 # that the OS and drives can reorder them. Same applies to
- 431 # "concurrent_counter_writes", since counter writes read the current
- 432 # values before incrementing and writing them back.
- 433 #
- 434 # On the other hand, since writes are almost never IO bound, the ideal
- 435 # number of "concurrent_writes" is dependent on the number of cores in
- 436 # your system; (8 * number_of_cores) is a good rule of thumb.
- 437 concurrent_reads: 32
- 438 concurrent_writes: 32
- 439 concurrent_counter_writes: 32
- 440
- 441 # For materialized view writes, as there is a read involved, so this should
- 442 # be limited by the less of concurrent reads or concurrent writes.
- 443 concurrent_materialized_view_writes: 32
- 444
- 445 # Maximum memory to use for sstable chunk cache and buffer pooling.
- 446 # 32MB of this are reserved for pooling buffers, the rest is used as an
- 447 # cache that holds uncompressed sstable chunks.
- 448 # Defaults to the smaller of 1/4 of heap or 512MB. This pool is allocated off-heap,
- 449 # so is in addition to the memory allocated for heap. The cache also has on-heap
- 450 # overhead which is roughly 128 bytes per chunk (i.e. 0.2% of the reserved size
- 451 # if the default 64k chunk size is used).
- 452 # Memory is only allocated when needed.
- 453 # file_cache_size_in_mb: 512
- 454
- 455 # Flag indicating whether to allocate on or off heap when the sstable buffer
- 456 # pool is exhausted, that is when it has exceeded the maximum memory
- 457 # file_cache_size_in_mb, beyond which it will not cache buffers but allocate on request.
- 458
- 459 # buffer_pool_use_heap_if_exhausted: true
- 460
- 461 # The strategy for optimizing disk read
- 462 # Possible values are:
- 463 # ssd (for solid state disks, the default)
- 464 # spinning (for spinning disks)
- 465 # disk_optimization_strategy: ssd
- 466
- 467 # Total permitted memory to use for memtables. Cassandra will stop
- 468 # accepting writes when the limit is exceeded until a flush completes,
- 469 # and will trigger a flush based on memtable_cleanup_threshold
- 470 # If omitted, Cassandra will set both to 1/4 the size of the heap.
- 471 # memtable_heap_space_in_mb: 2048
- 472 # memtable_offheap_space_in_mb: 2048
- 473
- 474 # Ratio of occupied non-flushing memtable size to total permitted size
- 475 # that will trigger a flush of the largest memtable. Larger mct will
- 476 # mean larger flushes and hence less compaction, but also less concurrent
- 477 # flush activity which can make it difficult to keep your disks fed
- 478 # under heavy write load.
- 479 #
- 480 # memtable_cleanup_threshold defaults to 1 / (memtable_flush_writers + 1)
- 481 # memtable_cleanup_threshold: 0.11
- 482
- 483 # Specify the way Cassandra allocates and manages memtable memory.
- 484 # Options are:
- 485 #
- 486 # heap_buffers
- 487 # on heap nio buffers
- 488 #
- 489 # offheap_buffers
- 490 # off heap (direct) nio buffers
- 491 #
- 492 # offheap_objects
- 493 # off heap objects
- 494 memtable_allocation_type: heap_buffers
- 495
- 496 # Total space to use for commit logs on disk.
- 497 #
- 498 # If space gets above this value, Cassandra will flush every dirty CF
- 499 # in the oldest segment and remove it. So a small total commitlog space
- 500 # will tend to cause more flush activity on less-active columnfamilies.
- 501 #
- 502 # The default value is the smaller of 8192, and 1/4 of the total space
- 503 # of the commitlog volume.
- 504 #
- 505 # commitlog_total_space_in_mb: 8192
- 506
- 507 # This sets the amount of memtable flush writer threads. These will
- 508 # be blocked by disk io, and each one will hold a memtable in memory
- 509 # while blocked.
- 510 #
- 511 # memtable_flush_writers defaults to one per data_file_directory.
- 512 #
- 513 # If your data directories are backed by SSD, you can increase this, but
- 514 # avoid having memtable_flush_writers * data_file_directories > number of cores
- 515 #memtable_flush_writers: 1
- 516
- 517 # Total space to use for change-data-capture logs on disk.
- 518 #
- 519 # If space gets above this value, Cassandra will throw WriteTimeoutException
- 520 # on Mutations including tables with CDC enabled. A CDCCompactor is responsible
- 521 # for parsing the raw CDC logs and deleting them when parsing is completed.
- 522 #
- 523 # The default value is the min of 4096 mb and 1/8th of the total space
- 524 # of the drive where cdc_raw_directory resides.
- 525 # cdc_total_space_in_mb: 4096
- 526
- 527 # When we hit our cdc_raw limit and the CDCCompactor is either running behind
- 528 # or experiencing backpressure, we check at the following interval to see if any
- 529 # new space for cdc-tracked tables has been made available. Default to 250ms
- 530 # cdc_free_space_check_interval_ms: 250
- 531
- 532 # A fixed memory pool size in MB for for SSTable index summaries. If left
- 533 # empty, this will default to 5% of the heap size. If the memory usage of
- 534 # all index summaries exceeds this limit, SSTables with low read rates will
- 535 # shrink their index summaries in order to meet this limit. However, this
- 536 # is a best-effort process. In extreme conditions Cassandra may need to use
- 537 # more than this amount of memory.
- 538 index_summary_capacity_in_mb:
- 539
- 540 # How frequently index summaries should be resampled. This is done
- 541 # periodically to redistribute memory from the fixed-size pool to sstables
- 542 # proportional their recent read rates. Setting to -1 will disable this
- 543 # process, leaving existing index summaries at their current sampling level.
- 544 index_summary_resize_interval_in_minutes: 60
- 545
- 546 # Whether to, when doing sequential writing, fsync() at intervals in
- 547 # order to force the operating system to flush the dirty
- 548 # buffers. Enable this to avoid sudden dirty buffer flushing from
- 549 # impacting read latencies. Almost always a good idea on SSDs; not
- 550 # necessarily on platters.
- 551 trickle_fsync: false
- 552 trickle_fsync_interval_in_kb: 10240
- 553
- 554 # TCP port, for commands and data
- 555 # For security reasons, you should not expose this port to the internet. Firewall it if needed.
- 556 storage_port: 7000
- 557
- 558 # SSL port, for encrypted communication. Unused unless enabled in
- 559 # encryption_options
- 560 # For security reasons, you should not expose this port to the internet. Firewall it if needed.
- 561 ssl_storage_port: 7001
- 562
- 563 # Address or interface to bind to and tell other Cassandra nodes to connect to.
- 564 # You _must_ change this if you want multiple nodes to be able to communicate!
- 565 #
- 566 # Set listen_address OR listen_interface, not both.
- 567 #
- 568 # Leaving it blank leaves it up to InetAddress.getLocalHost(). This
- 569 # will always do the Right Thing _if_ the node is properly configured
- 570 # (hostname, name resolution, etc), and the Right Thing is to use the
- 571 # address associated with the hostname (it might not be).
- 572 #
- 573 # Setting listen_address to 0.0.0.0 is always wrong.
- 574 #
- 575 listen_address: 172.15.14.106
- 576
- 577 # Set listen_address OR listen_interface, not both. Interfaces must correspond
- 578 # to a single address, IP aliasing is not supported.
- 579 # listen_interface: eth0
- 580
- 581 # If you choose to specify the interface by name and the interface has an ipv4 and an ipv6 address
- 582 # you can specify which should be chosen using listen_interface_prefer_ipv6. If false the first ipv4
- 583 # address will be used. If true the first ipv6 address will be used. Defaults to false preferring
- 584 # ipv4. If there is only one address it will be selected regardless of ipv4/ipv6.
- 585 # listen_interface_prefer_ipv6: false
- 586
- 587 # Address to broadcast to other Cassandra nodes
- 588 # Leaving this blank will set it to the same value as listen_address
- 589 # broadcast_address: 1.2.3.4
- 590
- 591 # When using multiple physical network interfaces, set this
- 592 # to true to listen on broadcast_address in addition to
- 593 # the listen_address, allowing nodes to communicate in both
- 594 # interfaces.
- 595 # Ignore this property if the network configuration automatically
- 596 # routes between the public and private networks such as EC2.
- 597 # listen_on_broadcast_address: false
- 598
- 599 # Internode authentication backend, implementing IInternodeAuthenticator;
- 600 # used to allow/disallow connections from peer nodes.
- 601 # internode_authenticator: org.apache.cassandra.auth.AllowAllInternodeAuthenticator
- 602
- 603 # Whether to start the native transport server.
- 604 # Please note that the address on which the native transport is bound is the
- 605 # same as the rpc_address. The port however is different and specified below.
- 606 start_native_transport: true
- 607 # port for the CQL native transport to listen for clients on
- 608 # For security reasons, you should not expose this port to the internet. Firewall it if needed.
- 609 native_transport_port: 9042
- 610 # Enabling native transport encryption in client_encryption_options allows you to either use
- 611 # encryption for the standard port or to use a dedicated, additional port along with the unencrypted
- 612 # standard native_transport_port.
- 613 # Enabling client encryption and keeping native_transport_port_ssl disabled will use encryption
- 614 # for native_transport_port. Setting native_transport_port_ssl to a different value
- 615 # from native_transport_port will use encryption for native_transport_port_ssl while
- 616 # keeping native_transport_port unencrypted.
- 617 # native_transport_port_ssl: 9142
- 618 # The maximum threads for handling requests when the native transport is used.
- 619 # This is similar to rpc_max_threads though the default differs slightly (and
- 620 # there is no native_transport_min_threads, idle threads will always be stopped
- 621 # after 30 seconds).
- 622 # native_transport_max_threads: 128
- 623 #
- 624 # The maximum size of allowed frame. Frame (requests) larger than this will
- 625 # be rejected as invalid. The default is 256MB. If you're changing this parameter,
- 626 # you may want to adjust max_value_size_in_mb accordingly.
- 627 # native_transport_max_frame_size_in_mb: 256
- 628
- 629 # The maximum number of concurrent client connections.
- 630 # The default is -1, which means unlimited.
- 631 # native_transport_max_concurrent_connections: -1
- 632
- 633 # The maximum number of concurrent client connections per source ip.
- 634 # The default is -1, which means unlimited.
- 635 # native_transport_max_concurrent_connections_per_ip: -1
- 636
- 637 # Whether to start the thrift rpc server.
- 638 start_rpc: true
- 639
- 640 # The address or interface to bind the Thrift RPC service and native transport
- 641 # server to.
- 642 #
- 643 # Set rpc_address OR rpc_interface, not both.
- 644 #
- 645 # Leaving rpc_address blank has the same effect as on listen_address
- 646 # (i.e. it will be based on the configured hostname of the node).
- 647 #
- 648 # Note that unlike listen_address, you can specify 0.0.0.0, but you must also
- 649 # set broadcast_rpc_address to a value other than 0.0.0.0.
- 650 #
- 651 # For security reasons, you should not expose this port to the internet. Firewall it if needed.
- 652 rpc_address: 172.15.14.106
- 653
- 654 # Set rpc_address OR rpc_interface, not both. Interfaces must correspond
- 655 # to a single address, IP aliasing is not supported.
- 656 # rpc_interface: eth1
- 657
- 658 # If you choose to specify the interface by name and the interface has an ipv4 and an ipv6 address
- 659 # you can specify which should be chosen using rpc_interface_prefer_ipv6. If false the first ipv4
- 660 # address will be used. If true the first ipv6 address will be used. Defaults to false preferring
- 661 # ipv4. If there is only one address it will be selected regardless of ipv4/ipv6.
- 662 # rpc_interface_prefer_ipv6: false
- 663
- 664 # port for Thrift to listen for clients on
- 665 rpc_port: 9160
- 666
- 667 # RPC address to broadcast to drivers and other Cassandra nodes. This cannot
- 668 # be set to 0.0.0.0. If left blank, this will be set to the value of
- 669 # rpc_address. If rpc_address is set to 0.0.0.0, broadcast_rpc_address must
- 670 # be set.
- 671 # broadcast_rpc_address: 1.2.3.4
- 672
- 673 # enable or disable keepalive on rpc/native connections
- 674 rpc_keepalive: true
- 675
- 676 # Cassandra provides two out-of-the-box options for the RPC Server:
- 677 #
- 678 # sync
- 679 # One thread per thrift connection. For a very large number of clients, memory
- 680 # will be your limiting factor. On a 64 bit JVM, 180KB is the minimum stack size
- 681 # per thread, and that will correspond to your use of virtual memory (but physical memory
- 682 # may be limited depending on use of stack space).
- 683 #
- 684 # hsha
- 685 # Stands for "half synchronous, half asynchronous." All thrift clients are handled
- 686 # asynchronously using a small number of threads that does not vary with the amount
- 687 # of thrift clients (and thus scales well to many clients). The rpc requests are still
- 688 # synchronous (one thread per active request). If hsha is selected then it is essential
- 689 # that rpc_max_threads is changed from the default value of unlimited.
- 690 #
- 691 # The default is sync because on Windows hsha is about 30% slower. On Linux,
- 692 # sync/hsha performance is about the same, with hsha of course using less memory.
- 693 #
- 694 # Alternatively, can provide your own RPC server by providing the fully-qualified class name
- 695 # of an o.a.c.t.TServerFactory that can create an instance of it.
- 696 rpc_server_type: sync
- 697
- 698 # Uncomment rpc_min|max_thread to set request pool size limits.
- 699 #
- 700 # Regardless of your choice of RPC server (see above), the number of maximum requests in the
- 701 # RPC thread pool dictates how many concurrent requests are possible (but if you are using the sync
- 702 # RPC server, it also dictates the number of clients that can be connected at all).
- 703 #
- 704 # The default is unlimited and thus provides no protection against clients overwhelming the server. You are
- 705 # encouraged to set a maximum that makes sense for you in production, but do keep in mind that
- 706 # rpc_max_threads represents the maximum number of client requests this server may execute concurrently.
- 707 #
- 708 # rpc_min_threads: 16
- 709 # rpc_max_threads: 2048
- 710
- 711 # uncomment to set socket buffer sizes on rpc connections
- 712 # rpc_send_buff_size_in_bytes:
- 713 # rpc_recv_buff_size_in_bytes:
- 714
- 715 # Uncomment to set socket buffer size for internode communication
- 716 # Note that when setting this, the buffer size is limited by net.core.wmem_max
- 717 # and when not setting it it is defined by net.ipv4.tcp_wmem
- 718 # See also:
- 719 # /proc/sys/net/core/wmem_max
- 720 # /proc/sys/net/core/rmem_max
- 721 # /proc/sys/net/ipv4/tcp_wmem
- 722 # /proc/sys/net/ipv4/tcp_wmem
- 723 # and 'man tcp'
- 724 # internode_send_buff_size_in_bytes:
- 725
- 726 # Uncomment to set socket buffer size for internode communication
- 727 # Note that when setting this, the buffer size is limited by net.core.wmem_max
- 728 # and when not setting it it is defined by net.ipv4.tcp_wmem
- 729 # internode_recv_buff_size_in_bytes:
- 730
- 731 # Frame size for thrift (maximum message length).
- 732 thrift_framed_transport_size_in_mb: 15
- 733
- 734 # Set to true to have Cassandra create a hard link to each sstable
- 735 # flushed or streamed locally in a backups/ subdirectory of the
- 736 # keyspace data. Removing these links is the operator's
- 737 # responsibility.
- 738 incremental_backups: false
- 739
- 740 # Whether or not to take a snapshot before each compaction. Be
- 741 # careful using this option, since Cassandra won't clean up the
- 742 # snapshots for you. Mostly useful if you're paranoid when there
- 743 # is a data format change.
- 744 snapshot_before_compaction: false
- 745
- 746 # Whether or not a snapshot is taken of the data before keyspace truncation
- 747 # or dropping of column families. The STRONGLY advised default of true
- 748 # should be used to provide data safety. If you set this flag to false, you will
- 749 # lose data on truncation or drop.
- 750 auto_snapshot: true
- 751
- 752 # Granularity of the collation index of rows within a partition.
- 753 # Increase if your rows are large, or if you have a very large
- 754 # number of rows per partition. The competing goals are these:
- 755 #
- 756 # - a smaller granularity means more index entries are generated
- 757 # and looking up rows withing the partition by collation column
- 758 # is faster
- 759 # - but, Cassandra will keep the collation index in memory for hot
- 760 # rows (as part of the key cache), so a larger granularity means
- 761 # you can cache more hot rows
- 762 column_index_size_in_kb: 64
- 763
- 764 # Per sstable indexed key cache entries (the collation index in memory
- 765 # mentioned above) exceeding this size will not be held on heap.
- 766 # This means that only partition information is held on heap and the
- 767 # index entries are read from disk.
- 768 #
- 769 # Note that this size refers to the size of the
- 770 # serialized index information and not the size of the partition.
- 771 column_index_cache_size_in_kb: 2
- 772
- 773 # Number of simultaneous compactions to allow, NOT including
- 774 # validation "compactions" for anti-entropy repair. Simultaneous
- 775 # compactions can help preserve read performance in a mixed read/write
- 776 # workload, by mitigating the tendency of small sstables to accumulate
- 777 # during a single long running compactions. The default is usually
- 778 # fine and if you experience problems with compaction running too
- 779 # slowly or too fast, you should look at
- 780 # compaction_throughput_mb_per_sec first.
- 781 #
- 782 # concurrent_compactors defaults to the smaller of (number of disks,
- 783 # number of cores), with a minimum of 2 and a maximum of 8.
- 784 #
- 785 # If your data directories are backed by SSD, you should increase this
- 786 # to the number of cores.
- 787 #concurrent_compactors: 1
- 788
- 789 # Throttles compaction to the given total throughput across the entire
- 790 # system. The faster you insert data, the faster you need to compact in
- 791 # order to keep the sstable count down, but in general, setting this to
- 792 # 16 to 32 times the rate you are inserting data is more than sufficient.
- 793 # Setting this to 0 disables throttling. Note that this account for all types
- 794 # of compaction, including validation compaction.
- 795 compaction_throughput_mb_per_sec: 16
- 796
- 797 # When compacting, the replacement sstable(s) can be opened before they
- 798 # are completely written, and used in place of the prior sstables for
- 799 # any range that has been written. This helps to smoothly transfer reads
- 800 # between the sstables, reducing page cache churn and keeping hot rows hot
- 801 sstable_preemptive_open_interval_in_mb: 50
- 802
- 803 # Throttles all outbound streaming file transfers on this node to the
- 804 # given total throughput in Mbps. This is necessary because Cassandra does
- 805 # mostly sequential IO when streaming data during bootstrap or repair, which
- 806 # can lead to saturating the network connection and degrading rpc performance.
- 807 # When unset, the default is 200 Mbps or 25 MB/s.
- 808 # stream_throughput_outbound_megabits_per_sec: 200
- 809
- 810 # Throttles all streaming file transfer between the datacenters,
- 811 # this setting allows users to throttle inter dc stream throughput in addition
- 812 # to throttling all network stream traffic as configured with
- 813 # stream_throughput_outbound_megabits_per_sec
- 814 # When unset, the default is 200 Mbps or 25 MB/s
- 815 # inter_dc_stream_throughput_outbound_megabits_per_sec: 200
- 816
- 817 # How long the coordinator should wait for read operations to complete
- 818 read_request_timeout_in_ms: 5000
- 819 # How long the coordinator should wait for seq or index scans to complete
- 820 range_request_timeout_in_ms: 10000
- 821 # How long the coordinator should wait for writes to complete
- 822 write_request_timeout_in_ms: 2000
- 823 # How long the coordinator should wait for counter writes to complete
- 824 counter_write_request_timeout_in_ms: 5000
- 825 # How long a coordinator should continue to retry a CAS operation
- 826 # that contends with other proposals for the same row
- 827 cas_contention_timeout_in_ms: 1000
- 828 # How long the coordinator should wait for truncates to complete
- 829 # (This can be much longer, because unless auto_snapshot is disabled
- 830 # we need to flush first so we can snapshot before removing the data.)
- 831 truncate_request_timeout_in_ms: 60000
- 832 # The default timeout for other, miscellaneous operations
- 833 request_timeout_in_ms: 10000
- 834
- 835 # Enable operation timeout information exchange between nodes to accurately
- 836 # measure request timeouts. If disabled, replicas will assume that requests
- 837 # were forwarded to them instantly by the coordinator, which means that
- 838 # under overload conditions we will waste that much extra time processing
- 839 # already-timed-out requests.
- 840 #
- 841 # Warning: before enabling this property make sure to ntp is installed
- 842 # and the times are synchronized between the nodes.
- 843 cross_node_timeout: false
- 844
- 845 # Set socket timeout for streaming operation.
- 846 # The stream session is failed if no data/ack is received by any of the participants
- 847 # within that period, which means this should also be sufficient to stream a large
- 848 # sstable or rebuild table indexes.
- 849 # Default value is 86400000ms, which means stale streams timeout after 24 hours.
- 850 # A value of zero means stream sockets should never time out.
- 851 # streaming_socket_timeout_in_ms: 86400000
- 852
- 853 # phi value that must be reached for a host to be marked down.
- 854 # most users should never need to adjust this.
- 855 # phi_convict_threshold: 8
- 856
- 857 # endpoint_snitch -- Set this to a class that implements
- 858 # IEndpointSnitch. The snitch has two functions:
- 859 #
- 860 # - it teaches Cassandra enough about your network topology to route
- 861 # requests efficiently
- 862 # - it allows Cassandra to spread replicas around your cluster to avoid
- 863 # correlated failures. It does this by grouping machines into
- 864 # "datacenters" and "racks." Cassandra will do its best not to have
- 865 # more than one replica on the same "rack" (which may not actually
- 866 # be a physical location)
- 867 #
- 868 # CASSANDRA WILL NOT ALLOW YOU TO SWITCH TO AN INCOMPATIBLE SNITCH
- 869 # ONCE DATA IS INSERTED INTO THE CLUSTER. This would cause data loss.
- 870 # This means that if you start with the default SimpleSnitch, which
- 871 # locates every node on "rack1" in "datacenter1", your only options
- 872 # if you need to add another datacenter are GossipingPropertyFileSnitch
- 873 # (and the older PFS). From there, if you want to migrate to an
- 874 # incompatible snitch like Ec2Snitch you can do it by adding new nodes
- 875 # under Ec2Snitch (which will locate them in a new "datacenter") and
- 876 # decommissioning the old ones.
- 877 #
- 878 # Out of the box, Cassandra provides:
- 879 #
- 880 # SimpleSnitch:
- 881 # Treats Strategy order as proximity. This can improve cache
- 882 # locality when disabling read repair. Only appropriate for
- 883 # single-datacenter deployments.
- 884 #
- 885 # GossipingPropertyFileSnitch
- 886 # This should be your go-to snitch for production use. The rack
- 887 # and datacenter for the local node are defined in
- 888 # cassandra-rackdc.properties and propagated to other nodes via
- 889 # gossip. If cassandra-topology.properties exists, it is used as a
- 890 # fallback, allowing migration from the PropertyFileSnitch.
- 891 #
- 892 # PropertyFileSnitch:
- 893 # Proximity is determined by rack and data center, which are
- 894 # explicitly configured in cassandra-topology.properties.
- 895 #
- 896 # Ec2Snitch:
- 897 # Appropriate for EC2 deployments in a single Region. Loads Region
- 898 # and Availability Zone information from the EC2 API. The Region is
- 899 # treated as the datacenter, and the Availability Zone as the rack.
- 900 # Only private IPs are used, so this will not work across multiple
- 901 # Regions.
- 902 #
- 903 # Ec2MultiRegionSnitch:
- 904 # Uses public IPs as broadcast_address to allow cross-region
- 905 # connectivity. (Thus, you should set seed addresses to the public
- 906 # IP as well.) You will need to open the storage_port or
- 907 # ssl_storage_port on the public IP firewall. (For intra-Region
- 908 # traffic, Cassandra will switch to the private IP after
- 909 # establishing a connection.)
- 910 #
- 911 # RackInferringSnitch:
- 912 # Proximity is determined by rack and data center, which are
- 913 # assumed to correspond to the 3rd and 2nd octet of each node's IP
- 914 # address, respectively. Unless this happens to match your
- 915 # deployment conventions, this is best used as an example of
- 916 # writing a custom Snitch class and is provided in that spirit.
- 917 #
- 918 # You can use a custom Snitch by setting this to the full class name
- 919 # of the snitch, which will be assumed to be on your classpath.
- 920
- 921 endpoint_snitch: GossipingPropertyFileSnitch
- 922
- 923 # controls how often to perform the more expensive part of host score
- 924 # calculation
- 925 dynamic_snitch_update_interval_in_ms: 100
- 926 # controls how often to reset all host scores, allowing a bad host to
- 927 # possibly recover
- 928 dynamic_snitch_reset_interval_in_ms: 600000
- 929 # if set greater than zero and read_repair_chance is < 1.0, this will allow
- 930 # 'pinning' of replicas to hosts in order to increase cache capacity.
- 931 # The badness threshold will control how much worse the pinned host has to be
- 932 # before the dynamic snitch will prefer other replicas over it. This is
- 933 # expressed as a double which represents a percentage. Thus, a value of
- 934 # 0.2 means Cassandra would continue to prefer the static snitch values
- 935 # until the pinned host was 20% worse than the fastest.
- 936 dynamic_snitch_badness_threshold: 0.1
- 937
- 938 # request_scheduler -- Set this to a class that implements
- 939 # RequestScheduler, which will schedule incoming client requests
- 940 # according to the specific policy. This is useful for multi-tenancy
- 941 # with a single Cassandra cluster.
- 942 # NOTE: This is specifically for requests from the client and does
- 943 # not affect inter node communication.
- 944 # org.apache.cassandra.scheduler.NoScheduler - No scheduling takes place
- 945 # org.apache.cassandra.scheduler.RoundRobinScheduler - Round robin of
- 946 # client requests to a node with a separate queue for each
- 947 # request_scheduler_id. The scheduler is further customized by
- 948 # request_scheduler_options as described below.
- 949 request_scheduler: org.apache.cassandra.scheduler.NoScheduler
- 950
- 951 # Scheduler Options vary based on the type of scheduler
- 952 #
- 953 # NoScheduler
- 954 # Has no options
- 955 #
- 956 # RoundRobin
- 957 # throttle_limit
- 958 # The throttle_limit is the number of in-flight
- 959 # requests per client. Requests beyond
- 960 # that limit are queued up until
- 961 # running requests can complete.
- 962 # The value of 80 here is twice the number of
- 963 # concurrent_reads + concurrent_writes.
- 964 # default_weight
- 965 # default_weight is optional and allows for
- 966 # overriding the default which is 1.
- 967 # weights
- 968 # Weights are optional and will default to 1 or the
- 969 # overridden default_weight. The weight translates into how
- 970 # many requests are handled during each turn of the
- 971 # RoundRobin, based on the scheduler id.
- 972 #
- 973 # request_scheduler_options:
- 974 # throttle_limit: 80
- 975 # default_weight: 5
- 976 # weights:
- 977 # Keyspace1: 1
- 978 # Keyspace2: 5
- 979
- 980 # request_scheduler_id -- An identifier based on which to perform
- 981 # the request scheduling. Currently the only valid option is keyspace.
- 982 # request_scheduler_id: keyspace
- 983
- 984 # Enable or disable inter-node encryption
- 985 # JVM defaults for supported SSL socket protocols and cipher suites can
- 986 # be replaced using custom encryption options. This is not recommended
- 987 # unless you have policies in place that dictate certain settings, or
- 988 # need to disable vulnerable ciphers or protocols in case the JVM cannot
- 989 # be updated.
- 990 # FIPS compliant settings can be configured at JVM level and should not
- 991 # involve changing encryption settings here:
- 992 # https://docs.oracle.com/javase/8/docs/technotes/guides/security/jsse/FIPS.html
- 993 # *NOTE* No custom encryption options are enabled at the moment
- 994 # The available internode options are : all, none, dc, rack
- 995 #
- 996 # If set to dc cassandra will encrypt the traffic between the DCs
- 997 # If set to rack cassandra will encrypt the traffic between the racks
- 998 #
- 999 # The passwords used in these options must match the passwords used when generating
- 1000 # the keystore and truststore. For instructions on generating these files, see:
- 1001 # http://download.oracle.com/javase/6/docs/technotes/guides/security/jsse/JSSERefGuide.html#CreateKeystore
- 1002 #
- 1003 server_encryption_options:
- 1004 internode_encryption: none
- 1005 keystore: conf/.keystore
- 1006 keystore_password: cassandra
- 1007 truststore: conf/.truststore
- 1008 truststore_password: cassandra
- 1009 # More advanced defaults below:
- 1010 # protocol: TLS
- 1011 # algorithm: SunX509
- 1012 # store_type: JKS
- 1013 # cipher_suites: [TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_DHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA]
- 1014 # require_client_auth: false
- 1015 # require_endpoint_verification: false
- 1016
- 1017 # enable or disable client/server encryption.
- 1018 client_encryption_options:
- 1019 enabled: false
- 1020 # If enabled and optional is set to true encrypted and unencrypted connections are handled.
- 1021 optional: false
- 1022 keystore: conf/.keystore
- 1023 keystore_password: cassandra
- 1024 # require_client_auth: false
- 1025 # Set trustore and truststore_password if require_client_auth is true
- 1026 # truststore: conf/.truststore
- 1027 # truststore_password: cassandra
- 1028 # More advanced defaults below:
- 1029 # protocol: TLS
- 1030 # algorithm: SunX509
- 1031 # store_type: JKS
- 1032 # cipher_suites: [TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_DHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA]
- 1033
- 1034 # internode_compression controls whether traffic between nodes is
- 1035 # compressed.
- 1036 # Can be:
- 1037 #
- 1038 # all
- 1039 # all traffic is compressed
- 1040 #
- 1041 # dc
- 1042 # traffic between different datacenters is compressed
- 1043 #
- 1044 # none
- 1045 # nothing is compressed.
- 1046 internode_compression: dc
- 1047
- 1048 # Enable or disable tcp_nodelay for inter-dc communication.
- 1049 # Disabling it will result in larger (but fewer) network packets being sent,
- 1050 # reducing overhead from the TCP protocol itself, at the cost of increasing
- 1051 # latency if you block for cross-datacenter responses.
- 1052 inter_dc_tcp_nodelay: false
- 1053
- 1054 # TTL for different trace types used during logging of the repair process.
- 1055 tracetype_query_ttl: 86400
- 1056 tracetype_repair_ttl: 604800
- 1057
- 1058 # By default, Cassandra logs GC Pauses greater than 200 ms at INFO level
- 1059 # This threshold can be adjusted to minimize logging if necessary
- 1060 # gc_log_threshold_in_ms: 200
- 1061
- 1062 # If unset, all GC Pauses greater than gc_log_threshold_in_ms will log at
- 1063 # INFO level
- 1064 # UDFs (user defined functions) are disabled by default.
- 1065 # As of Cassandra 3.0 there is a sandbox in place that should prevent execution of evil code.
- 1066 enable_user_defined_functions: false
- 1067
- 1068 # Enables scripted UDFs (JavaScript UDFs).
- 1069 # Java UDFs are always enabled, if enable_user_defined_functions is true.
- 1070 # Enable this option to be able to use UDFs with "language javascript" or any custom JSR-223 provider.
- 1071 # This option has no effect, if enable_user_defined_functions is false.
- 1072 enable_scripted_user_defined_functions: false
- 1073
- 1074 # The default Windows kernel timer and scheduling resolution is 15.6ms for power conservation.
- 1075 # Lowering this value on Windows can provide much tighter latency and better throughput, however
- 1076 # some virtualized environments may see a negative performance impact from changing this setting
- 1077 # below their system default. The sysinternals 'clockres' tool can confirm your system's default
- 1078 # setting.
- 1079 windows_timer_interval: 1
- 1080
- 1081
- 1082 # Enables encrypting data at-rest (on disk). Different key providers can be plugged in, but the default reads from
- 1083 # a JCE-style keystore. A single keystore can hold multiple keys, but the one referenced by
- 1084 # the "key_alias" is the only key that will be used for encrypt opertaions; previously used keys
- 1085 # can still (and should!) be in the keystore and will be used on decrypt operations
- 1086 # (to handle the case of key rotation).
- 1087 #
- 1088 # It is strongly recommended to download and install Java Cryptography Extension (JCE)
- 1089 # Unlimited Strength Jurisdiction Policy Files for your version of the JDK.
- 1090 # (current link: http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html)
- 1091 #
- 1092 # Currently, only the following file types are supported for transparent data encryption, although
- 1093 # more are coming in future cassandra releases: commitlog, hints
- 1094 transparent_data_encryption_options:
- 1095 enabled: false
- 1096 chunk_length_kb: 64
- 1097 cipher: AES/CBC/PKCS5Padding
- 1098 key_alias: testing:1
- 1099 # CBC IV length for AES needs to be 16 bytes (which is also the default size)
- 1100 # iv_length: 16
- 1101 key_provider:
- 1102 - class_name: org.apache.cassandra.security.JKSKeyProvider
- 1103 parameters:
- 1104 - keystore: conf/.keystore
- 1105 keystore_password: cassandra
- 1106 store_type: JCEKS
- 1107 key_password: cassandra
- 1108
- 1109
- 1110 #####################
- 1111 # SAFETY THRESHOLDS #
- 1112 #####################
- 1113
- 1114 # When executing a scan, within or across a partition, we need to keep the
- 1115 # tombstones seen in memory so we can return them to the coordinator, which
- 1116 # will use them to make sure other replicas also know about the deleted rows.
- 1117 # With workloads that generate a lot of tombstones, this can cause performance
- 1118 # problems and even exaust the server heap.
- 1119 # (http://www.datastax.com/dev/blog/cassandra-anti-patterns-queues-and-queue-like-datasets)
- 1120 # Adjust the thresholds here if you understand the dangers and want to
- 1121 # scan more tombstones anyway. These thresholds may also be adjusted at runtime
- 1122 # using the StorageService mbean.
- 1123 tombstone_warn_threshold: 1000
- 1124 tombstone_failure_threshold: 100000
- 1125
- 1126 # Log WARN on any batch size exceeding this value. 5kb per batch by default.
- 1127 # Caution should be taken on increasing the size of this threshold as it can lead to node instability.
- 1128 batch_size_warn_threshold_in_kb: 5
- 1129
- 1130 # Fail any batch exceeding this value. 50kb (10x warn threshold) by default.
- 1131 batch_size_fail_threshold_in_kb: 50
- 1132
- 1133 # Log WARN on any batches not of type LOGGED than span across more partitions than this limit
- 1134 unlogged_batch_across_partitions_warn_threshold: 10
- 1135
- 1136 # Log a warning when compacting partitions larger than this value
- 1137 compaction_large_partition_warning_threshold_mb: 100
- 1138
- 1139 # GC Pauses greater than gc_warn_threshold_in_ms will be logged at WARN level
- 1140 # Adjust the threshold based on your application throughput requirement
- 1141 # By default, Cassandra logs GC Pauses greater than 200 ms at INFO level
- 1142 gc_warn_threshold_in_ms: 1000
- 1143
- 1144 # Maximum size of any value in SSTables. Safety measure to detect SSTable corruption
- 1145 # early. Any value size larger than this threshold will result into marking an SSTable
- 1146 # as corrupted.
- 1147 # max_value_size_in_mb: 256
- 1148 #
- 1149 auto_bootstrap: false
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement