Changing App Service plan level on Azure makes meilisearch unresponsive

TL;DR

Use a local persistent disk instead; the team opened a docs issue to fix the template. All in all the whole application just becomes unusable and needs to be completely deleted.

Steps

1. [Kerollmops (maintainer)]: The task-queue corruption on Azure App Service comes from storage: the one-click template puts Meilisearch's data on a network share, and the LMDB backend does not support network filesystems. Changing the App Service plan moves the data and corrupts the DB. Use a local persistent disk instead; the team opened a docs issue to fix the template.

When to use

You are seeing this: Issue meilisearch/meilisearch#4123 (closed, 21 comments): Describe the bug When deploying Meilisearch on Azure with the one click template in the documentation and then changing the App Service Plan level, the application becomes "kind of" unresponsive. Use this skill when you run into "Changing App Service plan level on Azure makes meilisearch unresponsive".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

In the GitHub issue gh:meilisearch/meilisearch#4123 (https://github.com/meilisearch/meilisearch/issues/4123), the problem reported was: Issue meilisearch/meilisearch#4123 (closed, 21 comments): Describe the bug When deploying Meilisearch on Azure with the one click template in the documentation and then changing the App Service Plan level, the application becomes "kind of" unresponsive. This means that i.e. Index creation is not working or requesting Task status is returning 404's even though the tasks were clearly created. Some requests however still work normally like "client.getallstats()". All in all the whole application just becomes unusable and needs to be completely deleted. One can even select the highest level plan and still get this result. The verified resolution was: [Kerollmops (maintainer)]: The task-queue corruption on Azure App Service comes from storage: the one-click template puts Meilisearch's data on a network share, and the LMDB backend does not support network filesystems. Changing the App Service plan moves the data and corrupts the DB. Use a local persistent disk instead; the team opened a docs issue to fix the template.