Enabling HA and SDN on Existing Typesense Cloud Cluster
TLDR Ross asked about enabling HA and SDN on an existing Typesense Cloud cluster. Jason confirmed a resulting downtime and the need for a setup like Cloudflare DNS for maintaining same hostnames.
Jun 06, 2022 (17 months ago)
Ross
08:26 PMRoss
08:32 PMIs there any way to make the hostname for the SDN cluster the same as the existing (non-HA, non-SDN) cluster?
Jason
08:48 PMWe are unable to turn on SDN on an existing cluster, so I guess the questions don't apply.
> Is there any way to make the hostname for the SDN cluster the same as the existing (non-HA, non-SDN) cluster?
Not on the Typesense Cloud side, but if you setup something like Cloudflare DNS (with proxy turned on), then you can keep the hostnames the same across clusters.
Typesense
Indexed 2776 threads (79% resolved)
Similar Threads
Troubleshooting Typesense Cluster Sync Issues in K8s Environment
Robert encountered node syncing issues in the K8s cluster with Typesense nodes. Kishore Nallan offered advice, including using DNS names and suggesting a call. Robert plans to use a single region Typesense with Redis caching. The thread resolved with the possibility of configuring Typesense with DNS names from 0.21.0.
Troubleshooting Read Timeout Issues on AWS Cluster.
Stefan encountered read timeout issues with AWS cluster, and Kishore Nallan helped evaluate the issue, finding an unhealthy node which was fixed. Kishore Nallan also helped Stefan to upgrade the cluster configuration.
Troubleshooting IP Update on Kubernetes Typesense
Alessandro and Damien are having issues with old IP addresses in a Kubernetes Typesense cluster not being updated. Kishore Nallan provides possible troubleshooting solutions, and mentioned the need for a fix for DNS retries. A suggested update strategy was shared by Aljosa.