Dump import crashed when dump file is created out of empty MeiliSearch

[bidoubiwa]

Describe the bug
When creating a dump on an empty MeiliSearch instance, the dump is created correctly but when launching it using --import-dump the launch fails with the following error:

Error: No such file or directory (os error 2)

But the file does exists.

To Reproduce
Steps to reproduce the behavior:

1. Launch empty MeiliSearch instance
2. Create dump
3. Wait for dump completion
4. Stop and restart meilisearch with --import-dump
5. Error: Error: No such file or directory (os error 2)

Expected behavior
No crash

MeiliSearch version:
v0.22.0

[curquiza]

Thank you @bidoubiwa for this report!

[rubiagatra]

Hello @curquiza, I am using Meilisearch in production and I want to start to contribute.

This is a good first issue, Any idea how I can explore this one?

[irevoire]

Hi @rubiagatra.
I think I can give you some little hints,

1. When you generate a dump, the xxxxx-yyyyy.dump file generated is actually a .tar.gz file. So if you want to see the content of a dump you can run: tar xzf 20210920-091520164.dump to uncompress it.
2. The file creating the dump is located here: meilisearch-http/src/index_controller/dump_actor/actor.rs
3. The file extracting the dump is located here: meilisearch-http/src/index_controller/dump_actor/loaders/v2.rs

And to give you a vague idea of what is happening when we create a dump:

1. We stop everyone from doing anything with a “mutex tricks”
2. Then each actor dump itself

Also maybe you missed it but there is a little bit of documentation explaining how to navigate in the codebase: in the lib.rs