<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.0.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>DataStax Support Forums &#187; Topic: &#34;Loading OpsCenter...&#34; -&#62; &#34;Error loading cluster: Call to /nodes/all timed out.&#38;qu</title>
		<link>http://www.datastax.com/support-forums/topic/loading-opscenter-error-loading-cluster-call-to-nodesall-timed-out</link>
		<description>Software, Support, and Training for Apache Cassandra</description>
		<language>en-US</language>
		<pubDate>Fri, 24 May 2013 04:40:05 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.0.3</generator>
		<textInput>
			<title><![CDATA[Search]]></title>
			<description><![CDATA[Search all topics from these forums.]]></description>
			<name>q</name>
			<link>http://www.datastax.com/support-forums/search.php</link>
		</textInput>
		<atom:link href="http://www.datastax.com/support-forums/rss/topic/loading-opscenter-error-loading-cluster-call-to-nodesall-timed-out" rel="self" type="application/rss+xml" />

		<item>
			<title>mbulman on "&#34;Loading OpsCenter...&#34; -&#62; &#34;Error loading cluster: Call to /nodes/all timed out.&#38;qu"</title>
			<link>http://www.datastax.com/support-forums/topic/loading-opscenter-error-loading-cluster-call-to-nodesall-timed-out#post-164</link>
			<pubDate>Wed, 15 Jun 2011 18:51:44 +0000</pubDate>
			<dc:creator>mbulman</dc:creator>
			<guid isPermaLink="false">164@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;TheSaint, yeah.  BOP will be supported in our next release (1.2) which is slated for release around July 8 though.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>TheSaint on "&#34;Loading OpsCenter...&#34; -&#62; &#34;Error loading cluster: Call to /nodes/all timed out.&#38;qu"</title>
			<link>http://www.datastax.com/support-forums/topic/loading-opscenter-error-loading-cluster-call-to-nodesall-timed-out#post-163</link>
			<pubDate>Wed, 15 Jun 2011 18:50:09 +0000</pubDate>
			<dc:creator>TheSaint</dc:creator>
			<guid isPermaLink="false">163@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;mbulman, is this still the case and can this cause OpsCenter not to be able to connect to the cluster?&#60;/p&#62;
&#60;p&#62;&#34;OpsCenter doesn't currently work with clusters using ByteOrderPartitioner. RandomPartitioner and OrderPreservingPartitioner should both work fine though.&#34;
&#60;/p&#62;</description>
		</item>
		<item>
			<title>secu on "&#34;Loading OpsCenter...&#34; -&#62; &#34;Error loading cluster: Call to /nodes/all timed out.&#38;qu"</title>
			<link>http://www.datastax.com/support-forums/topic/loading-opscenter-error-loading-cluster-call-to-nodesall-timed-out#post-27</link>
			<pubDate>Mon, 09 May 2011 06:16:31 +0000</pubDate>
			<dc:creator>secu</dc:creator>
			<guid isPermaLink="false">27@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;Damned! I should read this before to struggle with Ops...
&#60;/p&#62;</description>
		</item>
		<item>
			<title>elz on "&#34;Loading OpsCenter...&#34; -&#62; &#34;Error loading cluster: Call to /nodes/all timed out.&#38;qu"</title>
			<link>http://www.datastax.com/support-forums/topic/loading-opscenter-error-loading-cluster-call-to-nodesall-timed-out#post-15</link>
			<pubDate>Fri, 22 Apr 2011 20:42:23 +0000</pubDate>
			<dc:creator>elz</dc:creator>
			<guid isPermaLink="false">15@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;Perfect, thankyou
&#60;/p&#62;</description>
		</item>
		<item>
			<title>mbulman on "&#34;Loading OpsCenter...&#34; -&#62; &#34;Error loading cluster: Call to /nodes/all timed out.&#38;qu"</title>
			<link>http://www.datastax.com/support-forums/topic/loading-opscenter-error-loading-cluster-call-to-nodesall-timed-out#post-8</link>
			<pubDate>Fri, 22 Apr 2011 18:22:04 +0000</pubDate>
			<dc:creator>mbulman</dc:creator>
			<guid isPermaLink="false">8@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;OpsCenter doesn't currently work with clusters using ByteOrderPartitioner.  RandomPartitioner and OrderPreservingPartitioner should both work fine though.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>elz on "&#34;Loading OpsCenter...&#34; -&#62; &#34;Error loading cluster: Call to /nodes/all timed out.&#38;qu"</title>
			<link>http://www.datastax.com/support-forums/topic/loading-opscenter-error-loading-cluster-call-to-nodesall-timed-out#post-7</link>
			<pubDate>Fri, 22 Apr 2011 18:08:16 +0000</pubDate>
			<dc:creator>elz</dc:creator>
			<guid isPermaLink="false">7@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;Hi,&#60;/p&#62;
&#60;p&#62;   I'm attempting to evaluate opscenter at the moment, but I'm having difficulty getting it to play ball on my single-node development machine:&#60;/p&#62;
&#60;p&#62;Ubuntu Maverick&#60;br /&#62;
Vanilla Cassandra 0.7.4 ( binary tarball install )&#60;/p&#62;
&#60;p&#62;Cassandra is running fine, and the OpsCenter daemon aptitude installation went without a hitch, but &#60;a href=&#34;http://localhost:8888&#34; rel=&#34;nofollow&#34;&#62;http://localhost:8888&#60;/a&#62; just gives me a &#34;Loading OpsCenter...&#34; page which will eventually timeout and popup a &#34;Error loading cluster: Call to /nodes/all timed out.&#34; message.&#60;/p&#62;
&#60;p&#62;I tried manually installing the opscenter agent, as per the install guide ( and the services seem to be running ) - but this didn't appear to help.&#60;/p&#62;
&#60;p&#62;I've also tried defining an rmi server host in cassandra-env.sh:&#60;/p&#62;
&#60;p&#62;JVM_OPTS=&#34;$JVM_OPTS -Djava.rmi.server.hostname=127.0.0.1&#34;&#60;/p&#62;
&#60;p&#62;Any pointers will be much appreciated&#60;/p&#62;
&#60;p&#62;Cheers,&#60;/p&#62;
&#60;p&#62;      Joe Fox&#60;/p&#62;
&#60;p&#62;&#60;code&#62;&#60;br /&#62;
-----------------------------------------------------&#60;/p&#62;
&#60;p&#62;elzorro   7143  0.2  3.7 3554320 228036 pts/0  Sl   19:37   0:04 /usr/bin/java -ea -XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms2986M -Xmx2986M -Xmn746M -XX:+HeapDumpOnOutOfMemoryError -Xss128k -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:SurvivorRatio=8 -XX:MaxTenuringThreshold=1 -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -Djava.net.preferIPv4Stack=true -Djava.rmi.server.hostname=127.0.0.1 -Dcom.sun.management.jmxremote.port=8080 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Dlog4j.configuration=log4j-server.properties -Dlog4j.defaultInitOverride=true -Dcassandra-pidfile=cassandra.pid -cp bin/../conf:bin/../build/classes:bin/../lib/antlr-3.1.3.jar:bin/../lib/apache-cassandra-0.7.4.jar:bin/../lib/avro-1.4.0-fixes.jar:bin/../lib/avro-1.4.0-sources-fixes.jar:bin/../lib/commons-cli-1.1.jar:bin/../lib/commons-codec-1.2.jar:bin/../lib/commons-collections-3.2.1.jar:bin/../lib/commons-lang-2.4.jar:bin/../lib/concurrentlinkedhashmap-lru-1.1.jar:bin/../lib/guava-r05.jar:bin/../lib/high-scale-lib.jar:bin/../lib/jackson-core-asl-1.4.0.jar:bin/../lib/jackson-mapper-asl-1.4.0.jar:bin/../lib/jetty-6.1.21.jar:bin/../lib/jetty-util-6.1.21.jar:bin/../lib/jline-0.9.94.jar:bin/../lib/json-simple-1.1.jar:bin/../lib/jug-2.0.0.jar:bin/../lib/libthrift-0.5.jar:bin/../lib/log4j-1.2.16.jar:bin/../lib/mx4j-tools.jar:bin/../lib/servlet-api-2.5-20081211.jar:bin/../lib/slf4j-api-1.6.1.jar:bin/../lib/slf4j-log4j12-1.6.1.jar:bin/../lib/snakeyaml-1.6.jar org.apache.cassandra.thrift.CassandraDaemon&#60;br /&#62;
root      7350  0.0  0.3  86616 23008 ?        S    19:38   0:00 /usr/bin/python /usr/bin/twistd -u 0 -g 0 --pidfile /var/run/opscenter/opscenterd.pid -l /var/log/opscenter/opscenterd.log -y /usr/share/opscenter/bin/start_opscenter.py&#60;br /&#62;
root      7352  0.7  3.3 1997660 205640 ?      Sl   19:38   0:11 /usr/bin/java -Djava.library.path=/usr/lib/jni -Dpython.cachedir=/root/.jython_cache org.python.util.jython -jar /usr/share/opscenter/bin/jmxjython.jar -t 50 -k 60 --automated&#60;br /&#62;
root      9349  0.0  0.0  21784  1836 ?        S    20:02   0:00 /bin/bash /opt/opscenter/usr/share/opscenter-agent/bin/opscenter_agent_monitor&#60;br /&#62;
root      9360  0.0  0.2  71816 14004 ?        S    20:02   0:00 /usr/bin/python /usr/bin/twistd --pidfile /var/run/opscenter-agent/opscenter-agent.pid --syslog --prefix='opscenter-agent' -y /opt/opscenter/usr/share/opscenter-agent/bin/start_opscenter_agent.py&#60;br /&#62;
elzorro   9430  0.0  0.0  10112   868 pts/0    S+   20:04   0:00 grep --color=auto ops&#60;/p&#62;
&#60;p&#62;-------------------------------------------------&#60;/p&#62;
&#60;p&#62;Proto Recv-Q Send-Q Local Address           Foreign Address         State&#60;br /&#62;
tcp        0      0 127.0.0.1:9160          0.0.0.0:*               LISTEN&#60;br /&#62;
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN&#60;br /&#62;
tcp        0      0 127.0.0.1:8081          0.0.0.0:*               LISTEN&#60;br /&#62;
tcp        0      0 127.0.0.1:61619         0.0.0.0:*               LISTEN&#60;br /&#62;
tcp        0      0 0.0.0.0:61620           0.0.0.0:*               LISTEN&#60;br /&#62;
tcp        0      0 0.0.0.0:57717           0.0.0.0:*               LISTEN&#60;br /&#62;
tcp        0      0 127.0.0.1:8888          0.0.0.0:*               LISTEN&#60;br /&#62;
tcp        0      0 127.0.0.1:7000          0.0.0.0:*               LISTEN&#60;br /&#62;
tcp        0      0 0.0.0.0:48608           0.0.0.0:*               LISTEN&#60;/p&#62;
&#60;p&#62;------------------------------------------------------------&#60;/p&#62;
&#60;p&#62;2011-04-22 19:38:49+0200 [-] Log opened.&#60;br /&#62;
2011-04-22 19:38:49+0200 [-] twistd 10.2.0 (/usr/bin/python 2.6.6) starting up.&#60;br /&#62;
2011-04-22 19:38:49+0200 [-] reactor class: twisted.internet.selectreactor.SelectReactor.&#60;br /&#62;
2011-04-22 19:38:49+0200 [-] opscenterd.WebServer.OpsCenterdWebServer starting on 8888&#60;br /&#62;
2011-04-22 19:38:49+0200 [-] Starting factory &#38;lt;opscenterd.WebServer.OpsCenterdWebServer instance at 0x17a8b00&#38;gt;&#60;br /&#62;
2011-04-22 19:38:49+0200 [-] morbid.morbid.StompFactory starting on 61619&#60;br /&#62;
2011-04-22 19:38:49+0200 [-] Starting factory &#38;lt;morbid.morbid.StompFactory instance at 0x17c26c8&#38;gt;&#60;br /&#62;
2011-04-22 19:38:49+0200 [-] morbid.morbid.StompFactory starting on 61620&#60;br /&#62;
2011-04-22 19:38:49+0200 [-] set uid/gid 0/0&#60;br /&#62;
2011-04-22 19:38:49+0200 [-] OpsCenterdService startService&#60;br /&#62;
2011-04-22 19:38:49+0200 [-] JmxJythonService started. State is now &#34;startup&#34;.&#60;br /&#62;
2011-04-22 19:38:49+0200 [-] Starting CassandraCluster service&#60;br /&#62;
2011-04-22 19:38:49+0200 [-] Adding connection to &#38;lt;CassandraNode 127.0.0.1:9160 @0x17c6dd0&#38;gt;&#60;br /&#62;
2011-04-22 19:38:49+0200 [-] Adding connection to &#38;lt;CassandraNode 127.0.0.1:9160 @0x17c6dd0&#38;gt;&#60;br /&#62;
2011-04-22 19:38:49+0200 [-] Adding connection to &#38;lt;CassandraNode 127.0.0.1:9160 @0x17c6dd0&#38;gt;&#60;br /&#62;
2011-04-22 19:38:49+0200 [-] Adding connection to &#38;lt;CassandraNode 127.0.0.1:9160 @0x17c6dd0&#38;gt;&#60;br /&#62;
2011-04-22 19:38:49+0200 [-] Adding connection to &#38;lt;CassandraNode 127.0.0.1:9160 @0x17c6dd0&#38;gt;&#60;br /&#62;
2011-04-22 19:38:49+0200 [CassandraPoolParticipantClient,client] /usr/lib/pymodules/python2.6/telephus/pool.py:274: telephus.pool.NoKeyspacesAvailable: Can't gather information about the Cassandra ring; no non-system keyspaces available&#60;br /&#62;
2011-04-22 19:38:49+0200 [CassandraPoolParticipantClient,client] Successfully added connection to &#38;lt;CassandraNode 127.0.0.1:9160 @0x17c6dd0&#38;gt; to the pool&#60;br /&#62;
2011-04-22 19:38:49+0200 [CassandraPoolParticipantClient,client] Successfully added connection to &#38;lt;CassandraNode 127.0.0.1:9160 @0x17c6dd0&#38;gt; to the pool&#60;br /&#62;
2011-04-22 19:38:49+0200 [CassandraPoolParticipantClient,client] Successfully added connection to &#38;lt;CassandraNode 127.0.0.1:9160 @0x17c6dd0&#38;gt; to the pool&#60;br /&#62;
2011-04-22 19:38:49+0200 [CassandraPoolParticipantClient,client] Successfully added connection to &#38;lt;CassandraNode 127.0.0.1:9160 @0x17c6dd0&#38;gt; to the pool&#60;br /&#62;
2011-04-22 19:38:49+0200 [CassandraPoolParticipantClient,client] Successfully added connection to &#38;lt;CassandraNode 127.0.0.1:9160 @0x17c6dd0&#38;gt; to the pool&#60;br /&#62;
2011-04-22 19:38:49+0200 [CassandraPoolParticipantClient,client] acquired initial keyspace list: [CassandraKeyspace(keyspace=system, column_families=['IndexInfo', 'Schema', 'Migrations', 'LocationInfo', 'HintsColumnFamily'], attributes={'strategy_options': None, 'replica_placement_strategy': 'org.apache.cassandra.locator.LocalStrategy', 'replication_factor': 1})]&#60;br /&#62;
2011-04-22 19:38:49+0200 [CassandraPoolParticipantClient,client] acquired snitch: org.apache.cassandra.locator.SimpleSnitch&#60;br /&#62;
2011-04-22 19:38:49+0200 [CassandraPoolParticipantClient,client] acquired cluster name: Test Cluster&#60;br /&#62;
2011-04-22 19:38:49+0200 [CassandraPoolParticipantClient,client] acquired partitioner: org.apache.cassandra.dht.ByteOrderedPartitioner&#60;br /&#62;
2011-04-22 19:38:51+0200 [StompProtocol,0,127.0.0.1] agent for ip 127.0.0.1 is version u'1.0.0'&#60;br /&#62;
2011-04-22 19:38:53+0200 [-] JmxJythonService got jmxjython startup message. State is now &#34;normal&#34;.&#60;/p&#62;
&#60;p&#62;---------------------------------------------------------------&#60;/p&#62;
&#60;p&#62;# opscenterd.conf&#60;/p&#62;
&#60;p&#62;[jmx]&#60;br /&#62;
cassandra_classpath = /usr/share/opscenter/lib/*.jar&#60;br /&#62;
port = 8080&#60;/p&#62;
&#60;p&#62;[webserver]&#60;br /&#62;
port = 8888&#60;br /&#62;
interface = 127.0.0.1&#60;br /&#62;
staticdir = /usr/share/opscenter/content&#60;/p&#62;
&#60;p&#62;[cassandra]&#60;br /&#62;
forget_nodes_after = 2629800   ; average month&#60;/p&#62;
&#60;p&#62;# a comma-separated list of places to try for a connection to your Cassandra&#60;br /&#62;
# cluster:&#60;br /&#62;
seed_hosts = 127.0.0.1&#60;/p&#62;
&#60;p&#62;# the API (Thrift) port on your Cassandra cluster&#60;br /&#62;
api_port = 9160&#60;/p&#62;
&#60;p&#62;[collection]&#60;br /&#62;
basic_info_period = 3600&#60;br /&#62;
node_poll_period = 120&#60;/p&#62;
&#60;p&#62;[authentication]&#60;br /&#62;
# if this file does not exist, there will be no password protection. Use the&#60;br /&#62;
# set_passwd.py tool (included with OpsCenter) to set passwords.&#60;br /&#62;
passwd_file = /etc/opscenter/.passwd&#60;/p&#62;
&#60;p&#62;---------------------------------------------------------------------------&#60;/p&#62;
&#60;p&#62;# Cassandra storage config YAML &#60;/p&#62;
&#60;p&#62;# NOTE:&#60;br /&#62;
#   See &#60;a href=&#34;http://wiki.apache.org/cassandra/StorageConfiguration&#34; rel=&#34;nofollow&#34;&#62;http://wiki.apache.org/cassandra/StorageConfiguration&#60;/a&#62; for&#60;br /&#62;
#   full explanations of configuration directives&#60;br /&#62;
# /NOTE&#60;/p&#62;
&#60;p&#62;# The name of the cluster. This is mainly used to prevent machines in&#60;br /&#62;
# one logical cluster from joining another.&#60;br /&#62;
cluster_name: 'Test Cluster'&#60;/p&#62;
&#60;p&#62;# You should always specify InitialToken when setting up a production&#60;br /&#62;
# cluster for the first time, and often when adding capacity later.&#60;br /&#62;
# The principle is that each node should be given an equal slice of&#60;br /&#62;
# the token ring; see &#60;a href=&#34;http://wiki.apache.org/cassandra/Operations&#34; rel=&#34;nofollow&#34;&#62;http://wiki.apache.org/cassandra/Operations&#60;/a&#62;&#60;br /&#62;
# for more details.&#60;br /&#62;
#&#60;br /&#62;
# If blank, Cassandra will request a token bisecting the range of&#60;br /&#62;
# the heaviest-loaded existing node.  If there is no load information&#60;br /&#62;
# available, such as is the case with a new cluster, it will pick&#60;br /&#62;
# a random token, which will lead to hot spots.&#60;br /&#62;
initial_token:&#60;/p&#62;
&#60;p&#62;# Set to true to make new [non-seed] nodes automatically migrate data&#60;br /&#62;
# to themselves from the pre-existing nodes in the cluster.  Defaults&#60;br /&#62;
# to false because you can only bootstrap N machines at a time from&#60;br /&#62;
# an existing cluster of N, so if you are bringing up a cluster of&#60;br /&#62;
# 10 machines with 3 seeds you would have to do it in stages.  Leaving&#60;br /&#62;
# this off for the initial start simplifies that.&#60;br /&#62;
auto_bootstrap: false&#60;/p&#62;
&#60;p&#62;# See &#60;a href=&#34;http://wiki.apache.org/cassandra/HintedHandoff&#34; rel=&#34;nofollow&#34;&#62;http://wiki.apache.org/cassandra/HintedHandoff&#60;/a&#62;&#60;br /&#62;
hinted_handoff_enabled: true&#60;br /&#62;
# this defines the maximum amount of time a dead host will have hints&#60;br /&#62;
# generated.  After it has been dead this long, hints will be dropped.&#60;br /&#62;
max_hint_window_in_ms: 3600000 # one hour&#60;br /&#62;
# Sleep this long after delivering each row or row fragment&#60;br /&#62;
hinted_handoff_throttle_delay_in_ms: 50&#60;/p&#62;
&#60;p&#62;# authentication backend, implementing IAuthenticator; used to identify users&#60;br /&#62;
authenticator: org.apache.cassandra.auth.AllowAllAuthenticator&#60;/p&#62;
&#60;p&#62;# authorization backend, implementing IAuthority; used to limit access/provide permissions&#60;br /&#62;
authority: org.apache.cassandra.auth.AllowAllAuthority&#60;/p&#62;
&#60;p&#62;# The partitioner is responsible for distributing rows (by key) across&#60;br /&#62;
# nodes in the cluster.  Any IPartitioner may be used, including your&#60;br /&#62;
# own as long as it is on the classpath.  Out of the box, Cassandra&#60;br /&#62;
# provides org.apache.cassandra.dht.RandomPartitioner&#60;br /&#62;
# org.apache.cassandra.dht.ByteOrderedPartitioner,&#60;br /&#62;
# org.apache.cassandra.dht.OrderPreservingPartitioner (deprecated),&#60;br /&#62;
# and org.apache.cassandra.dht.CollatingOrderPreservingPartitioner&#60;br /&#62;
# (deprecated).&#60;br /&#62;
#&#60;br /&#62;
# - RandomPartitioner distributes rows across the cluster evenly by md5.&#60;br /&#62;
#   When in doubt, this is the best option.&#60;br /&#62;
# - ByteOrderedPartitioner orders rows lexically by key bytes.  BOP allows&#60;br /&#62;
#   scanning rows in key order, but the ordering can generate hot spots&#60;br /&#62;
#   for sequential insertion workloads.&#60;br /&#62;
# - OrderPreservingPartitioner is an obsolete form of BOP, that stores&#60;br /&#62;
# - keys in a less-efficient format and only works with keys that are&#60;br /&#62;
#   UTF8-encoded Strings.&#60;br /&#62;
# - CollatingOPP colates according to EN,US rules rather than lexical byte&#60;br /&#62;
#   ordering.  Use this as an example if you need custom collation.&#60;br /&#62;
#&#60;br /&#62;
# See &#60;a href=&#34;http://wiki.apache.org/cassandra/Operations&#34; rel=&#34;nofollow&#34;&#62;http://wiki.apache.org/cassandra/Operations&#60;/a&#62; for more on&#60;br /&#62;
# partitioners and token selection.&#60;br /&#62;
partitioner: org.apache.cassandra.dht.ByteOrderedPartitioner&#60;/p&#62;
&#60;p&#62;# directories where Cassandra should store data on disk.&#60;br /&#62;
data_file_directories:&#60;br /&#62;
    - /home/elzorro/projects/cassandra/database/data&#60;/p&#62;
&#60;p&#62;# commit log&#60;br /&#62;
commitlog_directory: /home/elzorro/projects/cassandra/database/commitlog&#60;/p&#62;
&#60;p&#62;# saved caches&#60;br /&#62;
saved_caches_directory: /home/elzorro/projects/cassandra/database/saved_caches&#60;/p&#62;
&#60;p&#62;# Size to allow commitlog to grow to before creating a new segment&#60;br /&#62;
commitlog_rotation_threshold_in_mb: 128&#60;/p&#62;
&#60;p&#62;# commitlog_sync may be either &#34;periodic&#34; or &#34;batch.&#34;&#60;br /&#62;
# When in batch mode, Cassandra won't ack writes until the commit log&#60;br /&#62;
# has been fsynced to disk.  It will wait up to&#60;br /&#62;
# CommitLogSyncBatchWindowInMS milliseconds for other writes, before&#60;br /&#62;
# performing the sync.&#60;br /&#62;
commitlog_sync: periodic&#60;/p&#62;
&#60;p&#62;# the other option is &#34;periodic&#34; where writes may be acked immediately&#60;br /&#62;
# and the CommitLog is simply synced every commitlog_sync_period_in_ms&#60;br /&#62;
# milliseconds.&#60;br /&#62;
commitlog_sync_period_in_ms: 10000&#60;/p&#62;
&#60;p&#62;# emergency pressure valve: each time heap usage after a full (CMS)&#60;br /&#62;
# garbage collection is above this fraction of the max, Cassandra will&#60;br /&#62;
# flush the largest memtables.&#60;br /&#62;
#&#60;br /&#62;
# Set to 1.0 to disable.  Setting this lower than&#60;br /&#62;
# CMSInitiatingOccupancyFraction is not likely to be useful.&#60;br /&#62;
#&#60;br /&#62;
# RELYING ON THIS AS YOUR PRIMARY TUNING MECHANISM WILL WORK POORLY:&#60;br /&#62;
# it is most effective under light to moderate load, or read-heavy&#60;br /&#62;
# workloads; under truly massive write load, it will often be too&#60;br /&#62;
# little, too late.&#60;br /&#62;
flush_largest_memtables_at: 0.75&#60;/p&#62;
&#60;p&#62;# emergency pressure valve #2: the first time heap usage after a full&#60;br /&#62;
# (CMS) garbage collection is above this fraction of the max,&#60;br /&#62;
# Cassandra will reduce cache maximum _capacity_ to the given fraction&#60;br /&#62;
# of the current _size_.  Should usually be set substantially above&#60;br /&#62;
# flush_largest_memtables_at, since that will have less long-term&#60;br /&#62;
# impact on the system.&#60;br /&#62;
#&#60;br /&#62;
# Set to 1.0 to disable.  Setting this lower than&#60;br /&#62;
# CMSInitiatingOccupancyFraction is not likely to be useful.&#60;br /&#62;
reduce_cache_sizes_at: 0.85&#60;br /&#62;
reduce_cache_capacity_to: 0.6&#60;/p&#62;
&#60;p&#62;# Addresses of hosts that are deemed contact points.&#60;br /&#62;
# Cassandra nodes use this list of hosts to find each other and learn&#60;br /&#62;
# the topology of the ring.  You must change this if you are running&#60;br /&#62;
# multiple nodes!&#60;br /&#62;
seeds:&#60;br /&#62;
    - 127.0.0.1&#60;/p&#62;
&#60;p&#62;# Access mode.  mmapped i/o is substantially faster, but only practical on&#60;br /&#62;
# a 64bit machine (which notably does not include EC2 &#34;small&#34; instances)&#60;br /&#62;
# or relatively small datasets.  &#34;auto&#34;, the safe choice, will enable&#60;br /&#62;
# mmapping on a 64bit JVM.  Other values are &#34;mmap&#34;, &#34;mmap_index_only&#34;&#60;br /&#62;
# (which may allow you to get part of the benefits of mmap on a 32bit&#60;br /&#62;
# machine by mmapping only index files) and &#34;standard&#34;.&#60;br /&#62;
# (The buffer size settings that follow only apply to standard,&#60;br /&#62;
# non-mmapped i/o.)&#60;br /&#62;
disk_access_mode: auto&#60;/p&#62;
&#60;p&#62;# For workloads with more data than can fit in memory, Cassandra's&#60;br /&#62;
# bottleneck will be reads that need to fetch data from&#60;br /&#62;
# disk. &#34;concurrent_reads&#34; should be set to (16 * number_of_drives) in&#60;br /&#62;
# order to allow the operations to enqueue low enough in the stack&#60;br /&#62;
# that the OS and drives can reorder them.&#60;br /&#62;
#&#60;br /&#62;
# On the other hand, since writes are almost never IO bound, the ideal&#60;br /&#62;
# number of &#34;concurrent_writes&#34; is dependent on the number of cores in&#60;br /&#62;
# your system; (8 * number_of_cores) is a good rule of thumb.&#60;br /&#62;
concurrent_reads: 16&#60;br /&#62;
concurrent_writes: 32&#60;/p&#62;
&#60;p&#62;# This sets the amount of memtable flush writer threads.  These will&#60;br /&#62;
# be blocked by disk io, and each one will hold a memtable in memory&#60;br /&#62;
# while blocked. If you have a large heap and many data directories,&#60;br /&#62;
# you can increase this value for better flush performance.&#60;br /&#62;
# By default this will be set to the amount of data directories defined.&#60;br /&#62;
#memtable_flush_writers: 1&#60;/p&#62;
&#60;p&#62;# Buffer size to use when performing contiguous column slices.&#60;br /&#62;
# Increase this to the size of the column slices you typically perform&#60;br /&#62;
sliced_buffer_size_in_kb: 64&#60;/p&#62;
&#60;p&#62;# TCP port, for commands and data&#60;br /&#62;
storage_port: 7000&#60;/p&#62;
&#60;p&#62;# Address to bind to and tell other Cassandra nodes to connect to. You&#60;br /&#62;
# _must_ change this if you want multiple nodes to be able to&#60;br /&#62;
# communicate!&#60;br /&#62;
#&#60;br /&#62;
# Leaving it blank leaves it up to InetAddress.getLocalHost(). This&#60;br /&#62;
# will always do the Right Thing *if* the node is properly configured&#60;br /&#62;
# (hostname, name resolution, etc), and the Right Thing is to use the&#60;br /&#62;
# address associated with the hostname (it might not be).&#60;br /&#62;
#&#60;br /&#62;
# Setting this to 0.0.0.0 is always wrong.&#60;br /&#62;
listen_address: localhost&#60;/p&#62;
&#60;p&#62;# The address to bind the Thrift RPC service to -- clients connect&#60;br /&#62;
# here. Unlike ListenAddress above, you *can* specify 0.0.0.0 here if&#60;br /&#62;
# you want Thrift to listen on all interfaces.&#60;br /&#62;
#&#60;br /&#62;
# Leaving this blank has the same effect it does for ListenAddress,&#60;br /&#62;
# (i.e. it will be based on the configured hostname of the node).&#60;br /&#62;
rpc_address: localhost&#60;br /&#62;
# port for Thrift to listen for clients on&#60;br /&#62;
rpc_port: 9160&#60;/p&#62;
&#60;p&#62;# enable or disable keepalive on rpc connections&#60;br /&#62;
rpc_keepalive: true&#60;/p&#62;
&#60;p&#62;# Cassandra uses thread-per-client for client RPC.  This can&#60;br /&#62;
# be expensive in memory used for thread stack for a large&#60;br /&#62;
# enough number of clients.  (Hence, connection pooling is&#60;br /&#62;
# very, very strongly recommended.)&#60;br /&#62;
#&#60;br /&#62;
# Uncomment rpc_min&#124;max&#124;thread to set request pool size.&#60;br /&#62;
# You would primarily set max as a safeguard against misbehaved&#60;br /&#62;
# clients; if you do hit the max, Cassandra will block until&#60;br /&#62;
# one disconnects before accepting more.  The defaults are&#60;br /&#62;
# min of 16 and max unlimited.&#60;br /&#62;
#&#60;br /&#62;
# rpc_min_threads: 16&#60;br /&#62;
# rpc_max_threads: 2048&#60;/p&#62;
&#60;p&#62;# uncomment to set socket buffer sizes on rpc connections&#60;br /&#62;
# rpc_send_buff_size_in_bytes:&#60;br /&#62;
# rpc_recv_buff_size_in_bytes:&#60;/p&#62;
&#60;p&#62;# Frame size for thrift (maximum field length).&#60;br /&#62;
# 0 disables TFramedTransport in favor of TSocket. This option&#60;br /&#62;
# is deprecated; we strongly recommend using Framed mode.&#60;br /&#62;
thrift_framed_transport_size_in_mb: 15&#60;/p&#62;
&#60;p&#62;# The max length of a thrift message, including all fields and&#60;br /&#62;
# internal thrift overhead.&#60;br /&#62;
thrift_max_message_length_in_mb: 16&#60;/p&#62;
&#60;p&#62;# Set to true to have Cassandra create a hard link to each sstable&#60;br /&#62;
# flushed or streamed locally in a backups/ subdirectory of the&#60;br /&#62;
# Keyspace data.  Removing these links is the operator's&#60;br /&#62;
# responsibility.&#60;br /&#62;
incremental_backups: false&#60;/p&#62;
&#60;p&#62;# Whether or not to take a snapshot before each compaction.  Be&#60;br /&#62;
# careful using this option, since Cassandra won't clean up the&#60;br /&#62;
# snapshots for you.  Mostly useful if you're paranoid when there&#60;br /&#62;
# is a data format change.&#60;br /&#62;
snapshot_before_compaction: false&#60;/p&#62;
&#60;p&#62;# change this to increase the compaction thread's priority.  In java, 1 is the&#60;br /&#62;
# lowest priority and that is our default.&#60;br /&#62;
# compaction_thread_priority: 1&#60;/p&#62;
&#60;p&#62;# Add column indexes to a row after its contents reach this size.&#60;br /&#62;
# Increase if your column values are large, or if you have a very large&#60;br /&#62;
# number of columns.  The competing causes are, Cassandra has to&#60;br /&#62;
# deserialize this much of the row to read a single column, so you want&#60;br /&#62;
# it to be small - at least if you do many partial-row reads - but all&#60;br /&#62;
# the index data is read for each access, so you don't want to generate&#60;br /&#62;
# that wastefully either.&#60;br /&#62;
column_index_size_in_kb: 64&#60;/p&#62;
&#60;p&#62;# Size limit for rows being compacted in memory.  Larger rows will spill&#60;br /&#62;
# over to disk and use a slower two-pass compaction process.  A message&#60;br /&#62;
# will be logged specifying the row key.&#60;br /&#62;
in_memory_compaction_limit_in_mb: 64&#60;/p&#62;
&#60;p&#62;# Track cached row keys during compaction, and re-cache their new&#60;br /&#62;
# positions in the compacted sstable.  Disable if you use really large&#60;br /&#62;
# key caches.&#60;br /&#62;
compaction_preheat_key_cache: true&#60;/p&#62;
&#60;p&#62;# Time to wait for a reply from other nodes before failing the command&#60;br /&#62;
rpc_timeout_in_ms: 10000&#60;/p&#62;
&#60;p&#62;# phi value that must be reached for a host to be marked down.&#60;br /&#62;
# most users should never need to adjust this.&#60;br /&#62;
# phi_convict_threshold: 8&#60;/p&#62;
&#60;p&#62;# endpoint_snitch -- Set this to a class that implements&#60;br /&#62;
# IEndpointSnitch, which will let Cassandra know enough&#60;br /&#62;
# about your network topology to route requests efficiently.&#60;br /&#62;
# Out of the box, Cassandra provides&#60;br /&#62;
#  - org.apache.cassandra.locator.SimpleSnitch:&#60;br /&#62;
#    Treats Strategy order as proximity. This improves cache locality&#60;br /&#62;
#    when disabling read repair, which can further improve throughput.&#60;br /&#62;
#  - org.apache.cassandra.locator.RackInferringSnitch:&#60;br /&#62;
#    Proximity is determined by rack and data center, which are&#60;br /&#62;
#    assumed to correspond to the 3rd and 2nd octet of each node's&#60;br /&#62;
#    IP address, respectively&#60;br /&#62;
# org.apache.cassandra.locator.PropertyFileSnitch:&#60;br /&#62;
#  - Proximity is determined by rack and data center, which are&#60;br /&#62;
#    explicitly configured in cassandra-topology.properties.&#60;br /&#62;
endpoint_snitch: org.apache.cassandra.locator.SimpleSnitch&#60;/p&#62;
&#60;p&#62;# dynamic_snitch -- This boolean controls whether the above snitch is&#60;br /&#62;
# wrapped with a dynamic snitch, which will monitor read latencies&#60;br /&#62;
# and avoid reading from hosts that have slowed (due to compaction,&#60;br /&#62;
# for instance)&#60;br /&#62;
dynamic_snitch: true&#60;br /&#62;
# controls how often to perform the more expensive part of host score&#60;br /&#62;
# calculation&#60;br /&#62;
dynamic_snitch_update_interval_in_ms: 100&#60;br /&#62;
# controls how often to reset all host scores, allowing a bad host to&#60;br /&#62;
# possibly recover&#60;br /&#62;
dynamic_snitch_reset_interval_in_ms: 600000&#60;br /&#62;
# if set greater than zero and read_repair_chance is &#38;lt; 1.0, this will allow&#60;br /&#62;
# 'pinning' of replicas to hosts in order to increase cache capacity.&#60;br /&#62;
# The badness threshold will control how much worse the pinned host has to be&#60;br /&#62;
# before the dynamic snitch will prefer other replicas over it.  This is&#60;br /&#62;
# expressed as a double which represents a percentage.  Thus, a value of&#60;br /&#62;
# 0.2 means Cassandra would continue to prefer the static snitch values&#60;br /&#62;
# until the pinned host was 20% worse than the fastest.&#60;br /&#62;
dynamic_snitch_badness_threshold: 0.0&#60;/p&#62;
&#60;p&#62;# request_scheduler -- Set this to a class that implements&#60;br /&#62;
# RequestScheduler, which will schedule incoming client requests&#60;br /&#62;
# according to the specific policy. This is useful for multi-tenancy&#60;br /&#62;
# with a single Cassandra cluster.&#60;br /&#62;
# NOTE: This is specifically for requests from the client and does&#60;br /&#62;
# not affect inter node communication.&#60;br /&#62;
# org.apache.cassandra.scheduler.NoScheduler - No scheduling takes place&#60;br /&#62;
# org.apache.cassandra.scheduler.RoundRobinScheduler - Round robin of&#60;br /&#62;
# client requests to a node with a separate queue for each&#60;br /&#62;
# request_scheduler_id. The scheduler is further customized by&#60;br /&#62;
# request_scheduler_options as described below.&#60;br /&#62;
request_scheduler: org.apache.cassandra.scheduler.NoScheduler&#60;/p&#62;
&#60;p&#62;# Scheduler Options vary based on the type of scheduler&#60;br /&#62;
# NoScheduler - Has no options&#60;br /&#62;
# RoundRobin&#60;br /&#62;
#  - throttle_limit -- The throttle_limit is the number of in-flight&#60;br /&#62;
#                      requests per client.  Requests beyond&#60;br /&#62;
#                      that limit are queued up until&#60;br /&#62;
#                      running requests can complete.&#60;br /&#62;
#                      The value of 80 here is twice the number of&#60;br /&#62;
#                      concurrent_reads + concurrent_writes.&#60;br /&#62;
#  - default_weight -- default_weight is optional and allows for&#60;br /&#62;
#                      overriding the default which is 1.&#60;br /&#62;
#  - weights -- Weights are optional and will default to 1 or the&#60;br /&#62;
#               overridden default_weight. The weight translates into how&#60;br /&#62;
#               many requests are handled during each turn of the&#60;br /&#62;
#               RoundRobin, based on the scheduler id.&#60;br /&#62;
#&#60;br /&#62;
# request_scheduler_options:&#60;br /&#62;
#    throttle_limit: 80&#60;br /&#62;
#    default_weight: 5&#60;br /&#62;
#    weights:&#60;br /&#62;
#      Keyspace1: 1&#60;br /&#62;
#      Keyspace2: 5&#60;/p&#62;
&#60;p&#62;# request_scheduler_id -- An identifer based on which to perform&#60;br /&#62;
# the request scheduling. Currently the only valid option is keyspace.&#60;br /&#62;
# request_scheduler_id: keyspace&#60;/p&#62;
&#60;p&#62;# The Index Interval determines how large the sampling of row keys&#60;br /&#62;
#  is for a given SSTable. The larger the sampling, the more effective&#60;br /&#62;
#  the index is at the cost of space.&#60;br /&#62;
index_interval: 128&#60;br /&#62;
&#60;/code&#62;
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
