FQDNs of OpenSearch hosts
To connect to a host, you need its fully qualified domain name (FQDN). You can use the FQDN of a particular host in the cluster or a special FQDN always pointing to the available host with the DASHBOARDS role.
Here is a host FQDN example:
rc1a-goh2a9tr********.mdb.yandexcloud.net
Getting a host FQDN
There are several ways to get a OpenSearch host's FQDN:
-
Look up the FQDN in the management console:
- Navigate
to the cluster page. - Open the Hosts section.
- Copy the Host FQDN column value.
- Navigate
-
In the management console
, copy the cluster connection command (it contains the host’s FQDN). To get this command, navigate to the cluster page and click Connect. -
Get the list of cluster hosts using the CLI or API.
Special FQDN
An FQDN in c-<cluster_ID>.rw.mdb.yandexcloud.net format always points to the available OpenSearch host with the DASHBOARDS role in the cluster. You can get the cluster ID with the list of clusters in the folder.
You can connect to hosts with the DATA role using a special FQDN with port 9200. In which case the load balancer located on the host with the DASHBOARDS role will redirect the request to one of the hosts with the DATA role using the round-robinDASHBOARDS role.
You can use a special FQDN to send requests to a specific host group with the DATA role. To do this, add the X-Yandex-OpenSearch-NodeGroup=<host_group_name> header to the request.
You can get the host group name with cluster details.
In clusters with several DATA or DASHBOARDS hosts, a special FQDN may be pointing to an unavailable host for some time. This is because it takes time to update DNS records for special FQDNs. If your request returns an error, repeat it later.
Tip
To reduce latency and mitigate risks during master failovers, we recommend setting the master manually.