MeiliSearch/meilisearch-lib/src/index_controller/dump_actor
Tamo c9c7da3626
fix(dump): Uncompress the dump IN the data.ms
When loading a dump with docker, we had two problems.
After creating a tempdirectory, uncompressing and re-indexing the dump:
1. We try to `move` the new “data.ms” onto the currently present
   one. The problem is that if the `data.ms` is a mount point because
   that's what peoples do with docker usually. We can't override
   a mount point, and thus we were throwing an error.
2. The tempdir is created in `/tmp`, which is usually quite small AND may not
   be on the same partition as the `data.ms`. This means when we tried to move
   the dump over the `data.ms`, it was also failing because we can't move data
   between two partitions.
==============
1 was fixed by deleting the *content* of the `data.ms` and moving the *content*
of the tempdir *inside* the `data.ms`. If someone tries to create volumes inside
the `data.ms` that's his problem, not ours.
2 was fixed by creating the tempdir *inside* of the `data.ms`. If a user mounted
its `data.ms` on a large partition, there is no reason he could not load a big
dump because his `/tmp` was too small. This solves the issue; now the dump is
extracted and indexed on the same partition the `data.ms` will lay.

fix #1833
2022-01-10 14:56:03 +01:00
..
compat feat(all): Task store 2021-12-02 20:14:42 +01:00
loaders bug(lib): drop env on last use 2021-12-16 10:57:55 +01:00
actor.rs feat(all): Task store 2021-12-02 20:14:42 +01:00
error.rs feat(auth): API keys 2021-12-06 09:52:41 +01:00
handle_impl.rs feat(all): Task store 2021-12-02 20:14:42 +01:00
message.rs split meilisearch-http and meilisearch-lib 2021-09-21 13:23:22 +02:00
mod.rs fix(dump): Uncompress the dump IN the data.ms 2022-01-10 14:56:03 +01:00