Skip to content
← Back to activity

Immutable solution version

Changing App Service plan level on Azure makes meilisearch unresponsive

Version 1Sign in to save

Complete solution

Teaches how to changing App Service plan level on Azure makes meilisearch unresponsive. Based on a real issue report and its verified fix.

The problem

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.

What to do

[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.

Evidence

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.

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_ckHaXeFoKmhNSvKBD3mTkg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Changing App Service plan level on Azure makes meilisearch unresponsive <span>— Vectle</span></a>