Database Reference
In-Depth Information
Getting help from the mailing list
Cassandra is a robust and fault-tolerant software. It is possible that your production is run-
ning as expected while something is broken within. Replication and eventual consistency
can help you to build a robust application on top of Cassandra, but it is important to keep
an eye on monitoring statistics.
The tools that have been discussed in this and previous chapters should help you get
enough information about what went wrong. You should be able to fix common problems
using these tools. But sometimes it is a good idea to ask about a stubborn issue on the
When asking a question on the mailing list, provide as many statistics as you can gather
around the problem. Nodetool's
cfstats
,
tpstats
, and
ring
commands are common
ways to get Cassandra-specific statistics. You may want to check the Cassandra logs, en-
able
JVM_OPTS
for GC-related statistics, and profile using Java jhat or JConsole. Apart
from this, server specifications such as memory, CPU, network, and disk stats provide cru-
cial insights. Among other things, the following also repay consideration (as required) the
replication factor, compaction strategy, consistency level, and table specifications.
