#community-help

Cloud Cluster Node Down Due to DNS Issue

TLDR Alex reported issues with a specific node in their cloud cluster. Kishore Nallan identified and resolved a DNS-related problem with the node's hardware.

29mo

Join the chat

Jul 06, 2021 (29 months ago)

Photo of md5-faf0fdba0b6739a6706f05c15b6738c6

Alex

07:58 AM

Hi there, we are having issues with one of our nodes in our cloud cluster, is there an admin available that could help us with that?

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

08:00 AM

Hi Alex, can you please post the ID of your cluster?

Alex

08:05 AM

Hi Kishore, could it be qavk8i9comw5dsynp ?

Kishore Nallan

08:06 AM

The metrics look okay for me from our end. What issue are you facing?

Alex

08:07 AM

https://qavk8i9comw5dsynp-3.a1.typesense.net/health seems to be down, or?

08:08

Alex

08:08 AM

The other two respond with “ok”:true

Kishore Nallan

08:08 AM

Ok, checking.

08:19

Kishore Nallan

08:19 AM

Looks like the underlying node had a hardware failure and was replaced. There was an issue in DNS assignment. I have fixed it now and it should be available shortly once the DNS propagation happens.

08:19

Kishore Nallan

08:19 AM

We're already monitoring the underlying node health, but we have to improve our monitoring to also monitor the external DNS end-points. Sorry about that.

08:26

Kishore Nallan

08:26 AM

Alex https://qavk8i9comw5dsynp-3.a1.typesense.net/health is resolving now for me.

Alex

08:28 AM

I understand, thanks a lot for the help!

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 2779 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Upgrading Problems with Typesense Cloud Node

Alan encountered issues with their typesense cloud node during an import, resulting in the need for a manual upgrade. Kishore Nallan assisted with the upgrade process and Jason reported that an upgrade was queued due to a second outage.

12mo

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.

30mo

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.

27mo

ECONNRESET error on Typesense cloud

Masahiro was encountering connectivity issues in Typesense cloud, leading to "ECONNRESET" errors. After investigating and providing their cluster ID and endpoint to Jason, it was discovered that they set the wrong protocol in client initialization was wrong. The error was resolved.

31mo

Typesense Cluster Upgrade Issues and Solutions

Ken reported a system outage due to Typesense cluster upgrade issues. Jason recommended upgrading to the next RAM tier and explained when the auto upgrade feature takes effect. After a repeat issue, Jason added handling upgrades when disk space ran out to their backlog.