You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Andrew (Jira)" <ji...@apache.org> on 2024/06/21 11:17:00 UTC

[jira] [Created] (CASSANDRA-19722) Metric for Cross Node DC Latency records external DCs as UNKNOWN_DC until restart

Andrew created CASSANDRA-19722:
----------------------------------

             Summary: Metric for Cross Node DC Latency records external DCs as UNKNOWN_DC until restart
                 Key: CASSANDRA-19722
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19722
             Project: Cassandra
          Issue Type: Bug
            Reporter: Andrew


When creating a new DC for a different region (In this case, on AWS), I've noticed that the metric (JMX Exporter): `org.apache.cassandra.metrics:type=Messaging,name=*-Latency` shows `UNKNOWN_DC` for external datacenters until the node is restarted, at which point it seems to resolve to the actual datacenter name.

I'm using GossipingFileSnitch and nodetool status and nodetool gossipinfo always show the correct DC for the nodes, which makes me suspect there's some variable that's responsible for the metric that isn't updated



--
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