Distributed Search Network (DSN)
With the Distributed Search Network (DSN), you can add one or more servers to your cluster.
DSNs have these benefits:
-
Faster search. You can add DSN servers in regions close to your users. This reduces network latency which leads to faster searches.
-
Increased capacity. DSN servers add processing power to your cluster. Adding DSN servers in the same region as your main cluster can help with handling peak usage periods.
DSN servers are available as add-on to your subscription. For more information, see Pricing.
How DSN works
DSN servers aren’t backups. They’re independent duplicates of your cluster’s data and configuration.
After reaching consensus, the cluster finalizes its indexing tasks. The cluster sends this data to the DSN servers which then carry out the same indexing process. Depending on the size of the job, updates to a DSN server might be delayed by up to a few minutes.
DSN activation
After adding the DSN add-on to your subscription, Algolia initiates the distribution and synchronization of your data to your DSN servers.
To check the status of your DSN, go to the Algolia dashboard:
- On the left sidebar, select Settings.
- Open the Infrastructure page and go to the DSN tab.
Retry strategy
Algolia’s API clients select the nearest server (either DSN or your cluster) for search requests.
If a request fails, the clients follow this retry strategy:
- Connect to the cluster using one of its three server URLs.
- If this fails, try the second cluster URL.
- If this fails, try the third cluster URL.
- If this fails, report a timeout error.
DSN server URLs
Algolia’s DSN infrastructure is accessible through these URLs:
- Smart records (NS1)
{APPLICATION_ID}-dsn.algolia.net. Finds the closest server (from your cluster or a DSN server).{APPLICATION_ID}.algolia.net. Used for indexing.
-
Fallback records (Cloudflare) point to specific availability zones within your cluster:
{APPLICATION_ID}-1.algolianet.com{APPLICATION_ID}-2.algolianet.com{APPLICATION_ID}-3.algolianet.com
