QMS Configuration

This configuration - the endpoint and master key - is common to the whole installation, since there’s only ever one Meilisearch instance. Whether full text search is actually used, however, can be chosen for each tenant individually (list of tenants → tenant).

On a multi-tenant provider installation, the endpoint and master key are configured once, at the provider level:

Alongside the endpoint and master key, a status row reports on the Meilisearch instance as a whole:

Each individual tenant then has its own full text search statistics and reindexing controls, on that tenant’s own configuration page - see QMS Reindex.

On a single-tenant installation, there’s no separate provider-level page - the endpoint/master key configuration and the tenant’s own statistics and reindexing controls all appear together on the same page:

The connection fields and health status shown are the same ones described above for multi-tenant installations, just combined onto a single page. For the reindexing controls and per-tenant statistics also shown on this page, see QMS Reindex.

In a high availability (HA) deployment, the primary and secondary Data Services of a Data Service node must both use the same Meilisearch instance. Install Meilisearch only once, and do not install a separate instance on each node. Two instances would hold different indexes, and the search results would depend on which Data Service was active.

Because both Data Services must reach the same instance, the "Meilisearch Endpoint" cannot refer to the local machine:

Enter the "Meilisearch Endpoint" and "Meilisearch Master Key" as described in Enabling the feature. The values are common to the whole installation, so they are configured only once.

If the "Error" field is populated, QMS was unable to successfully communicate with the configured Meilisearch endpoint. Common values and what they indicate: