Clément Renault

> @gmourier 👍 already working with that version. That is strange that Meilisearch is crashing when only 20 task statuses are returned, the engine doesn't even deserialize the whole data...

Hey @chammika-become, I am sorry to announce to you that we prefer to close your PR as we would prefer to tackle the subject of _having better error messages_ in...

> Not sure I understand the concern here, the file are accessed only one, when the index is opened, and are lazily loaded on request so it doesn't affect startup...

Hello @neylsongularte, A solution you could use is to use only one index where you just add a `path` field to every document/block of text you have and [simply filter...

Thanks, @qdequele, for your review 🌮 > What are the risks and disadvantages of this solution? I needed to review the solution and it does absolutely not help regarding the...

Hey, I had an idea that maybe we could send a [429 Too Many Requests](http://web.archive.org/web/20210812043115/https://httpstatuses.com/429) instead of an internal error. But we could find more and better ideas by looking...

Why not but I find it a little bit more complex as there is more synchronization to do between thread and workers, also doing so forces us to share the...

What I worry about is that it is not recommended to keep a read transaction for too long as [it can block write transactions](https://pijul.org/posts/2021-01-15-sanakirja-locks/) (as there can only be 1...

Another solution could simply be to either: - Let the user specify how many parallel readers he wants to allow using a CLI argument. - Or multiply the number of...

So after reading a little bit more about [the consequences of setting this parameter to a high value](https://web.archive.org/web/20200112155415/https://twitter.com/armon/status/534867803426533376), we can as it doesn't impact performances.