Chapter 9. Failing Gracefully
Technology organizations, from the CTO to the system administrators, have spent countless hours over the years trying to prevent their database systems from experiencing failure. This is because failure typically meant downtime for the application or, even worse, a loss of critical data.
As we discussed in Chapter 1, Cassandra's Approach to High Availability, attempts to make these systems highly available often still required a significant amount of human intervention to restore functionality in the event of a failure. Cassandra, as we have learned, was designed from the ground up to consider failure as a normal operational state. This is because in a large distributed system, the chance that at any given moment a ...
Get Cassandra 3.x High Availability - Second Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
