text stringlengths 0 59.1k |
|---|
# For security reasons, you should not expose this port to the internet. Firewall it if needed. |
native_transport_port: 9042 |
# Enabling native transport encryption in client_encryption_options allows you to either use |
# encryption for the standard port or to use a dedicated, additional port along with the unencrypted |
# standard native_transport_port. |
# Enabling client encryption and keeping native_transport_port_ssl disabled will use encryption |
# for native_transport_port. Setting native_transport_port_ssl to a different value |
# from native_transport_port will use encryption for native_transport_port_ssl while |
# keeping native_transport_port unencrypted. |
# native_transport_port_ssl: 9142 |
# The maximum threads for handling requests when the native transport is used. |
# This is similar to rpc_max_threads though the default differs slightly (and |
# there is no native_transport_min_threads, idle threads will always be stopped |
# after 30 seconds). |
# native_transport_max_threads: 128 |
# |
# The maximum size of allowed frame. Frame (requests) larger than this will |
# be rejected as invalid. The default is 256MB. |
# native_transport_max_frame_size_in_mb: 256 |
# The maximum number of concurrent client connections. |
# The default is -1, which means unlimited. |
# native_transport_max_concurrent_connections: -1 |
# The maximum number of concurrent client connections per source ip. |
# The default is -1, which means unlimited. |
# native_transport_max_concurrent_connections_per_ip: -1 |
# Whether to start the thrift rpc server. |
start_rpc: false |
# The address or interface to bind the Thrift RPC service and native transport |
# server to. |
# |
# Set rpc_address OR rpc_interface, not both. Interfaces must correspond |
# to a single address, IP aliasing is not supported. |
# |
# Leaving rpc_address blank has the same effect as on listen_address |
# (i.e. it will be based on the configured hostname of the node). |
# |
# Note that unlike listen_address, you can specify 0.0.0.0, but you must also |
# set broadcast_rpc_address to a value other than 0.0.0.0. |
# |
# For security reasons, you should not expose this port to the internet. Firewall it if needed. |
# |
# If you choose to specify the interface by name and the interface has an ipv4 and an ipv6 address |
# you can specify which should be chosen using rpc_interface_prefer_ipv6. If false the first ipv4 |
# address will be used. If true the first ipv6 address will be used. Defaults to false preferring |
# ipv4. If there is only one address it will be selected regardless of ipv4/ipv6. |
rpc_address: localhost |
# rpc_interface: eth1 |
# rpc_interface_prefer_ipv6: false |
# port for Thrift to listen for clients on |
rpc_port: 9160 |
# RPC address to broadcast to drivers and other Cassandra nodes. This cannot |
# be set to 0.0.0.0. If left blank, this will be set to the value of |
# rpc_address. If rpc_address is set to 0.0.0.0, broadcast_rpc_address must |
# be set. |
# broadcast_rpc_address: 1.2.3.4 |
# enable or disable keepalive on rpc/native connections |
rpc_keepalive: true |
# Cassandra provides two out-of-the-box options for the RPC Server: |
# |
# sync -> One thread per thrift connection. For a very large number of clients, memory |
# will be your limiting factor. On a 64 bit JVM, 180KB is the minimum stack size |
# per thread, and that will correspond to your use of virtual memory (but physical memory |
# may be limited depending on use of stack space). |
# |
# hsha -> Stands for "half synchronous, half asynchronous." All thrift clients are handled |
# asynchronously using a small number of threads that does not vary with the amount |
# of thrift clients (and thus scales well to many clients). The rpc requests are still |
# synchronous (one thread per active request). If hsha is selected then it is essential |
# that rpc_max_threads is changed from the default value of unlimited. |
# |
# The default is sync because on Windows hsha is about 30% slower. On Linux, |
# sync/hsha performance is about the same, with hsha of course using less memory. |
# |
# Alternatively, can provide your own RPC server by providing the fully-qualified class name |
# of an o.a.c.t.TServerFactory that can create an instance of it. |
rpc_server_type: sync |
# Uncomment rpc_min|max_thread to set request pool size limits. |
# |
# Regardless of your choice of RPC server (see above), the number of maximum requests in the |
# RPC thread pool dictates how many concurrent requests are possible (but if you are using the sync |
# RPC server, it also dictates the number of clients that can be connected at all). |
# |
# The default is unlimited and thus provides no protection against clients overwhelming the server. You are |
# encouraged to set a maximum that makes sense for you in production, but do keep in mind that |
# rpc_max_threads represents the maximum number of client requests this server may execute concurrently. |
# |
# rpc_min_threads: 16 |
# rpc_max_threads: 2048 |
# uncomment to set socket buffer sizes on rpc connections |
# rpc_send_buff_size_in_bytes: |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.