anchor.diff:  # enable or disable keepalive on rpc connections
   rpc_keepalive: true
   
  -# Cassandra provides three 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, 128KB 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).
  +# Cassandra provides three options for the RPC Server:
  +#
  +# sync  -> One connection per thread in the rpc pool (see below).
  +#          For a very large number of clients, memory will be your limiting
  +#          factor; on a 64 bit JVM, 128KB is the minimum stack size per thread.
  +#          Connection pooling is very, very strongly recommended.
  +#
  +# async -> Nonblocking server implementation with one thread to serve 
  +#          rpc connections.  This is not recommended for high throughput use
  +#          cases. Async has been tested to be about 50% slower than sync
  +#          or hsha and is deprecated: it will be removed in the next major release.
  +#
  +# hsha  -> Stands for "half synchronous, half asynchronous." The rpc thread pool 
  +#          (see below) is used to manage requests, but the threads are multiplexed
  +#          across the different clients.
   #
   # 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 provide 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.
  +# Uncomment rpc_min|max|thread to set request pool size.
  +# You would primarily set max for the sync server to safeguard against
  +# misbehaved clients; if you do hit the max, Cassandra will block until one
  +# disconnects before accepting more.  The defaults for sync are min of 16 and max
  +# unlimited.
  +# 
  +# For the Hsha server, the min and max both default to quadruple the number of
  +# CPU cores.
  +#
  +# This configuration is ignored by the async server.
   #
   # rpc_min_threads: 16
   # rpc_max_threads: 2048
  
positive.code: # given total throughput in Mbps. This is necessary because Cassandra does
  # mostly sequential IO when streaming data during bootstrap or repair, which
  # can lead to saturating the network connection and degrading rpc performance.
  # When unset, the default is 200 Mbps or 25 MB/s.
  # stream_throughput_outbound_megabits_per_sec: 200
  
  # How long the coordinator should wait for read operations to complete
  read_request_timeout_in_ms: 10000
  # How long the coordinator should wait for seq or index scans to complete
  range_request_timeout_in_ms: 10000
  # How long the coordinator should wait for writes to complete
  write_request_timeout_in_ms: 10000
  # How long the coordinator should wait for truncates to complete
  # (This can be much longer, because unless auto_snapshot is disabled
  # we need to flush first so we can snapshot before removing the data.)
  truncate_request_timeout_in_ms: 60000
  # The default timeout for other, miscellaneous operations
  request_timeout_in_ms: 10000
  
  # Enable operation timeout information exchange between nodes to accurately
  # measure request timeouts, If disabled cassandra will assuming the request
  # was forwarded to the replica instantly by the coordinator
  #
  # Warning: before enabling this property make sure to ntp is installed
  # and the times are synchronized between the nodes.
  cross_node_timeout: false
  
  # Enable socket timeout for streaming operation.
  # When a timeout occurs during streaming, streaming is retried from the start
  
negative.code: # one logical cluster from joining another.
  cluster_name: 'Test Cluster'
  
  # You should always specify InitialToken when setting up a production
  # cluster for the first time, and often when adding capacity later.
  # The principle is that each node should be given an equal slice of
  # the token ring; see http://wiki.apache.org/cassandra/Operations
  