Moving Apache Cassandra command execution and monitoring from JMX to CQL: A Developer's Overview
summary
A proposal migrates Cassandra management and monitoring from JMX to the CQL/binary protocol by placing commands and metrics into central registries, generating dynamic MBeans and CQL exporters, and adding updatable virtual tables merged into 5.1 for settings and per-metric access; fetching a metric by key runs in sub-millisecond to millisecond range; the codebase currently contains 164 commands to surface and the plan uses a command registry and dynamic MBeans so a single implementation becomes available across JMX, REST and CQL.
AI-written summary · about
chapters (8)
- 0:00Introduction and motivation
- 1:56Concerns about JMX
- 4:28Management and metrics issues
- 7:57Implementation approach
- 10:08Virtual tables for metrics
- 11:15Command registry design
- 13:44Types of commands
- 17:42Centralized registry concept
related talks
28mScraping Your Cassandra Metrics - the Right Way, and the Dirty Way
45mFrom SQL to Cassandra
29mCassandra - an introduction
32mMigrating Applications Between Cassandra Clusters with No Downtime
35mThe What and Why of Cassandra Datamodelling at Scale
32mMigrating Workloads from Mainframes to Cassandra - Problems, Experience and Learnings
45mCassandra Architecture: Understanding, Scaling and Optimizing
31mApache Cassandra Analytics: A Recipe to Move Petabytes of Data