Is this a way that could be used, perhaps?
http://tech.superhappykittymeow.com/?p=296
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
I think I will try this. Worst case is that I scrap the indexes on
disk, and build up new indexes from S3.
(And an even worse case is that I will have to refeed the data, but even
that is no tragedy)
--
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/874n5qdyoi.fsf%40dod.no.
For more options, visit https://groups.google.com/groups/opt_out.
