just to clarify, local default gateway is what you specify in "path.data"
what i want to achieve from s3 is to handle a scenario where my node that
uses local ephemeral disk as local data store and then due to some outage
or crash, the local data is lost/corrupted. i should be easily able to
create another instance and point it to s3 and then it restores all the
data locally on that machine and is able to serve data and index data..
is that clear?
On Wed, Jul 18, 2012 at 1:41 PM, Shay Banon email@example.com wrote:
Its recommended to use the default local gateway even on AWS. No need to
move to s3 gateway really.
On Wed, Jul 18, 2012 at 12:21 PM, T Vinod Gupta firstname.lastname@example.org:
i tried different routes and still not able to get it to work. any ideas?
i even tried copying the whole data dir structure on s3 and using the
same name as cluster name and yet didnt work.. ES would empty out the
cluster name dir.
On Tue, Jul 17, 2012 at 4:10 PM, T Vinod Gupta email@example.com:
i have a running ES cluster (of 1 node only) on ec2 with lots of data on
it.. this is without ec2 plugin and any gateway. now i want to configure a
s3 gateway on top of it. but if i follow the steps in the tutorial, it ends
up deleting my index! how do i get around this problem? is it even possible?
i took a copy of the data as a backup and hence i am able to retry
multiple times by restoring the data back..
ps - i followed the steps in the tutorial with a new cluster and it
works perfectly. also, for my experiments, i am renaming the cluster by
simply renaming the cluster name dir in data dir.