Louis Dureuil

Hello, > I suggest an option to reset Meilisearch to its initial state. It is unclear to me if the option should be available in Meilisearch or in the Azure...

Hello :wave: as there hasn't been any movement on this issue for a while, and we're not going to address supporting Meilisearch on filesystems not supported by LMDB, I'm going...

Hello @Kerollmops, Something unclear to me: how do we go from the 500ms processing time (indicating an issue already because the processing time should not go >50ms) to >10s response...

Hello @MTRNord :wave: Unfortunately, you ran into a bug of the engine. I'm sorry this affected you 😞 To fix that bug we'll need a way to reproduce it. I...

Hello Nextra :wave:, Several people running Azure reported being affected by what looks like DB corruptions: https://github.com/meilisearch/meilisearch/issues/4123 Apparently it is due to the kind of storage used, which is unfortunately...

Quickly looking at the code of our database backend (LMDB), the MDB_PANIC can happen if: 1. The call to `msync` to flush data from the mmap to the backing file...

> This setup has worked pretty much uninterrupted for this whole year, the issues only started arising when I upgraded to 1.5 when it got released Did you perhaps restart...

Hello :wave: As we're not going to address supporting the discussed Azure setup for now, I'm closing this. Thank you for your report, feel free to reopen if you deem...

Thanks for the update. I can't think of anything in RC3 that would make things better. That's the good kind of mysterious though I guess 😅

Hello @surenderaphro, Thanks for opening the issue. We need more information to hopefully reproduce and fix it. Could you please provide: 1. The version of Meilisearch you're using 2. The...