[ 
https://issues.apache.org/jira/browse/CASSANDRA-20026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17913847#comment-17913847
 ] 

Caleb Rackliffe edited comment on CASSANDRA-20026 at 1/16/25 8:14 PM:
----------------------------------------------------------------------

5.0 CI results: [^ci_summary-1.html]

Again, the {{TableStatsTest}} failure seems to be the only real issue. 
Everything else looks like tests that pass locally or are just CI environment 
artifacts/timeouts and CASSANDRA-18440.

 


was (Author: maedhroz):
5.0 CI results: [^ci_summary-1.html]

Again, the {{TableStatsTest}} failure seems to be the only real issue. 
Everything else looks like tests that pass locally or are just CI environment 
artifacts/timeouts.

> 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: ci_summary-1.html, ci_summary.html, nodetool tablestats 
> output.png, result_details.tar-1.gz, result_details.tar.gz
>
>
> 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]

Reply via email to