Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Cassandra 3.x High Availability
  • Toc
  • feedback
Cassandra 3.x High Availability

Cassandra 3.x High Availability

By : Strickland
3.8 (6)
close
Cassandra 3.x High Availability

Cassandra 3.x High Availability

3.8 (6)
By: Strickland

Overview of this book

Apache Cassandra is a massively scalable, peer-to-peer database designed for 100 percent uptime, with deployments in the tens of thousands of nodes, all supporting petabytes of data. This book offers a practical insight into building highly available, real-world applications using Apache Cassandra. The book starts with the fundamentals, helping you to understand how Apache Cassandra’s architecture allows it to achieve 100 percent uptime when other systems struggle to do so. You’ll get an excellent understanding of data distribution, replication, and Cassandra’s highly tunable consistency model. Then we take an in-depth look at Cassandra's robust support for multiple data centers, and you’ll see how to scale out a cluster. Next, the book explores the domain of application design, with chapters discussing the native driver and data modeling. Lastly, you’ll find out how to steer clear of common anti-patterns and take advantage of Cassandra’s ability to fail gracefully.
Table of Contents (10 chapters)
close

Logging


In addition to keeping an eye on JMX statistics, there are several levels of log files that should be monitored so that they can be analyzed in case of failure. Ideally, you should be using some sort of log aggregation (such as Flume, FluentD, Splunk, or other similar tools) to make it easier to make sense of logs. Also, aggregation ensures that catastrophic node failures don't prevent you from recovering logs from the problematic hosts, which may be the most important bit of diagnostic data available.

Cassandra logs

Cassandra itself provides two logs, and both are located in the configured logging directory, which is /var/log/cassandra by default. The first, system.log, is a rolling log of Cassandra's logback output. The second, output.log, shows standard out and standard error and is overwritten on startup.

If you are experiencing an issue that warrants lower-level logging than the default INFO level, you can adjust the logging level by editing the logback.xml file (in the conf directory...

bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete