[
https://issues.apache.org/jira/browse/CASSANDRA-20026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909432#comment-17909432
]
Matt Byrd commented on CASSANDRA-20026:
---------------------------------------
It might overcomplicate things somewhat, but I did have the thought that it
might make sense to only emit SAI stats, if there is actually a secondary
attached index on the table.
Otherwise we're going to add a lot less useful output for the majority of
use-cases not using SAI.
I guess it may also make parsing the output less standard, but if
operators/users are parsing, hopefully they're doing so with json format and
can perhaps default values, also there appears to be some precedent for that,
with all the various checks for if (table.compressionMetadataOffHeapUsed) etc
etc.
> Integrate SAI's index state and query performance metrics w/ nodetool
> tablestats
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-20026
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20026
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Feature/SAI, Tool/nodetool
> Reporter: Caleb Rackliffe
> Assignee: Sunil Ramchandra Pawar
> Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Attachments: nodetool tablestats output.png
>
>
> The output structure of {{nodetool tablestats}} might be amenable to adding a
> number of SAI state/performance metrics, which are predominantly
> table-scoped. (There are some that are scoped at the column level, of course,
> but the table-level items could be useful if we don't want to directly call
> JMX and want a general idea of how we're doing with things like
> post-filtering read latency.)
> The decisions we have to make are along the lines of "What percentile to use
> for post-filtering read latency?", but I imagine we can follow whatever
> existing pattern exists.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
