[
https://issues.apache.org/jira/browse/CASSANDRA-19722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-19722:
-----------------------------------------
Bug Category: Parent values: Correctness(12982)
Complexity: Normal
Component/s: Observability/Metrics
Discovered By: User Report
Fix Version/s: 4.1.x
5.0.x
5.x
Severity: Normal
Status: Open (was: Triage Needed)
> 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
> Components: Observability/Metrics
> Reporter: Andrew
> Priority: Normal
> Fix For: 4.1.x, 5.0.x, 5.x
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
