cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Corentin Chary (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-13338) JMX: EstimatedPartitionCount / SnapshotSize are expensive
Date Thu, 16 Mar 2017 12:59:41 GMT
Corentin Chary created CASSANDRA-13338:
------------------------------------------

             Summary: JMX: EstimatedPartitionCount / SnapshotSize are expensive
                 Key: CASSANDRA-13338
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13338
             Project: Cassandra
          Issue Type: Improvement
          Components: Observability
            Reporter: Corentin Chary


EstimatedPartitionCount / EstimatedRowCount / SnapshotSize seem particularly expensive. For
example on our system org.apache.cassandra.metrics:type=ColumnFamily,name=SnapshotsSize can
take as much as half a second.

All this cumulated means that export stats for all your tables (with metrics-graphite or jmx_exporter)
is going to take quite some time.

We should certainly try to find the most expensive end points and see if there is a way to
cache some of the values.

cc: [~rgerard]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message