Open pvb05 opened 5 months ago
Hello @pvb05 , this is indeed a strange behaviour.
I tried to reproduce this myself, but with listing the backups. In both cases (medusa list-backups
and hitting the GetBackups
GRPC endpoint), it resolved into the pod name and I saw a line like:
[2024-06-11 12:14:15,498] DEBUG: Blob foo/foo-dc1-r1-sts-0/backup-2024-05-07t09-15-05-652z/meta/schema.cql was not found in cache.
So there are a few things I'd like to ask you in attempt to narrow this down:
medusa
CLI and the GRPC service run with the same ini file?cassandra/resolve_ip_addresses
field set to?
Project board link
Hi, I have Medusa 0.21 running in gRPC mode alongside Cassandra in a pod and when I invoke backup directly from the terminal of the Medusa container, the hostname is resolved and it creates and uploads to the corresponding node directory. But when I use a Medusa client to take a backup, it instead uses the node name and does not resolve to the correct hostname.
# LOGS WHEN INVOKED VIA MEDUSA GRPC CLIENT, Node hostname picked up - ip-192-168-125-141
# LOGS WHEN INVOKED FROM THE MEDUSA CONTAINER. Node hostname picked up - cassdata-dc1-0
I did not set storage.fqdn in medusa.ini hoping it to resolve on its own.
Can someone guide me get this behavior corrected?
thanks, Pradeep
┆Issue is synchronized with this Jira Story by Unito ┆Issue Number: MED-8