As your two DCs are in different AWS regions you may well see some lag between the two. This does depend on the amount of data being synced across the DCs. If you have large column families and / or a high level of writes then this will only mean more data to sync. Using LOCAL_QUORUM
is the right choice for keeping writes in the local DC. You could use a lower consistency level if you wanted, generally speaking if data consistency is important the rule of thumb is always to write at a higher consistency level than your reads.
Aside from the usual OS-level tools, Cassandra does have the nodetool
utility. For monitoring you can use the following nodetool
commands:
nodetool netstats
- (shows you if the node is streaming data) http://www.datastax.com/documentation/cassandra/2.0/cassandra/tools/toolsNetstats.html
nodetool cfstats
- (shows column family stats useful for latency etc) http://www.datastax.com/documentation/cassandra/2.0/cassandra/tools/toolsCFstats.html
nodetool proxyhistograms
- (shows stats from the co-ordinator nodes) http://www.datastax.com/documentation/cassandra/2.0/cassandra/tools/toolsProxyHistograms.html
There are also a number of other very useful nodetool commands, that you can use:
http://www.datastax.com/documentation/cassandra/2.0/cassandra/tools/toolsNodetool_r.html
I'm assuming you are using Cassandra 2.0 but for other versions a lot of the commands are similar for nodetool
As a side note, you can also use OpsCenter which gives a graphical view of the cluster, for more info see: http://www.datastax.com/documentation/opscenter/5.0/opsc/about_c.html