You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Yifan Cai (Jira)" <ji...@apache.org> on 2025/01/31 21:56:00 UTC
[jira] [Updated] (CASSSIDECAR-192) Fix Cassandra instance not found error
[ https://issues.apache.org/jira/browse/CASSSIDECAR-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yifan Cai updated CASSSIDECAR-192:
----------------------------------
Bug Category: Parent values: Availability(12983)Level 1 values: Response Crash(12991)
Complexity: Normal
Discovered By: User Report
Severity: Normal
Status: Open (was: Triage Needed)
> Fix Cassandra instance not found error
> --------------------------------------
>
> Key: CASSSIDECAR-192
> URL: https://issues.apache.org/jira/browse/CASSSIDECAR-192
> Project: Sidecar for Apache Cassandra
> Issue Type: Bug
> Components: Rest API
> Reporter: Yifan Cai
> Assignee: Yifan Cai
> Priority: Major
>
> {color:#000000}There is a bug in Sidecar's instance metadata lookup implementation can result into cassandra instance not found error. {color}
> {color:#000000}The error is reproduced when sidecar.yaml configures the FQDNs of Cassandra instances, but the sidecar clients use IP address to look up the Cassandra instance. {color}
> {color:#000000}The patch fixes the issue. {color}
> {color:#000000}The issue is also reported in the cassandra-sidecar slack channel by a user.{color}
--
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