We have learned a lot about monitoring, alerting, and logging tools, which can be used for troubleshooting an unexpected issue and resolving it faster and more easily. In distributed systems such as Cassandra, it would be very hard to find which node has the issue and whether it's related to the application, resource cap, resource steal, network outage, disk corruption, inappropriate Cassandra parameters, and so on. Going through all the nodes with a checklist is also tiresome. But with this kind of setup, we would be notified of any key issues that get triggered with alerting, and we can pinpoint the corresponding node. This reduces the effort of digging through all the nodes. With all this set up, it would a piece of cake ...
Troubleshooting
Get Mastering Apache Cassandra 3.x - Third 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.
