>>>>> Steinar Bang <[email protected]>: > Is this a way that could be used, perhaps? > http://tech.superhappykittymeow.com/?p=296
I tried, but no luck, I'm afraid. > Ie. > 1. Put the S3 stuff back into /etc/elasticsearch/elasticsearch.yml > 2. Restart ES, and hopefully it will find the stuff it needs in S3 and > come up with the two indexes > 3. Use the curl/sed commands in the above URL to extract metadata from > port 9200 > 4. Remove the S3 stuff from /etc/elasticsearch/elasticsearch.yml > 5. Restart ES, and it again will be unable to load the indexes, because > of the missing metadata > 6. Use curl to PUT the saved metadata into port 9200 At this stage I had the metadata for the indexes in place, but no documents in either index. Then I took a restart of ES, and it came up with the two indexes empty still, and the old data om /data/elasticsearch removed. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/87zjnichtg.fsf%40dod.no. For more options, visit https://groups.google.com/groups/opt_out.
