> I got the same behaviour when /var/lib/elasticsearch/elasticsearch was a > dangling symlink (...) so I thought it might be storage related...? >
Hmm, still, Elasticsearch should complain in the logs when the data dir is not accessible. Might be related to S3 gateway... > Is there something else I could use instead when I run out of > space on the instance itself? Because I fill up the disk on the > instance pretty quickly. Very good option on EC2 are EBS volumes, notably the IOPS (optimized or high I/O) ones. You can easily create snapshots, unmount the volume and mount it at different instance, etc. (Some people also use ephemeral disks (which are *huge* for reasonably large instances), and simply use lots of replicas to guard against data loss...) Karel P. S. The http://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/ tutorial, though quite old, is well worth thorough reading for understanding all the mechanics on EC2. There's another tutorial, http://www.elasticsearch.org/tutorials/deploying-elasticsearch-with-chef-solo/, which automates many of the steps with Chef. -- 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/c33370fe-7ec4-4a2a-941a-b77cd8a3203c%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
