Closed dmitrizagidulin closed 11 years ago
Ok, the error above results from backing up the _rsid_*
buckets (such as the _rsid_test_bucket
that automatically gets created in the repro steps above).
These are internal-use only buckets created by Riak Search, and contain the documents that search actually indexed.
The to-do issue for filtering them out is here: https://github.com/basho/riak-data-migrator/issues/4
As for this bug, for current versions of the DataMigrator, it can be avoided by manually deleting _rsid_*
directories in the exported data dirs. I'll add that to the README notes.
Closing.
To reproduce: On a riak 1.3 devrel build, with backend
riak_kv_eleveldb_backend
, riak Search enabled, and the following default properties in app.config (these shouldn't matter, adding them for completeness):{anti_entropy, {on, []}}
Launch riak, enable indexing on a bucket, and insert a test object:
Double-check the bucket list:
Now back up the cluster via DataMigrator 0.2.5:
Stop riak and clear the data directory:
Now, restoring the buckets via DataMigrator without re-enabling Search indexing on those buckets works just fine. But, if you enable indexing and try to restore, it errors out:
Data migrator error log contents:
Riak error log contents
At this point (after trying to restore search-indexed buckets via DataMigrator), a plain HTTP put to the same bucket results in the same error:
So, something is getting borked during the restoration process.