[jira] [Updated] (CASSANDRA-20017) Accord metrics are isolated which cause existing coordination metrics to be empty, should also populate there as well

["David Capwell (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-20017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Capwell updated CASSANDRA-20017:
--------------------------------------
     Bug Category: Parent values: Correctness(12982)Level 1 values: Consistency(12989)
       Complexity: Low Hanging Fruit
    Discovered By: Performance Regression Test
         Severity: Critical
           Status: Open  (was: Triage Needed)

> Accord metrics are isolated which cause existing coordination metrics to be empty, should also populate there as well
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-20017
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20017
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Accord
>            Reporter: David Capwell
>            Assignee: David Capwell
>            Priority: Normal
>
> When using Accord the latency/timeout metrics are isolated to accord, which breaks existing monitoring as it looks like the cluster is idle due to no traffic… we should also populate the coordination metrics as well like how paxos does



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org