>>>>> Steinar Bang <[email protected]>: > My problem now is that if I set data.path to in > /etc/elasticsearch/elasticsearch.yml to /mnt/elasticsearch (to get > ephemeral storage, since my main problem here is running out of disk > space on an EC2 instance that is started and stopped) then the EC2 > discovery and S3 settings seem to be skipped.
> Here is the complete elasticsearch.yml file with keys XXX'd: > https://gist.github.com/steinarb/8094353 I figured out what the problem was: I had a leading space in the line with the path.data setting, ie. path.data=/mnt/elasticsearch instead of path.data=/mnt/elasticsearch Once I removed the space, things started working. Ie. they startet working, *if* /mnt/elasticsearch existed and *if* it was writable by elasticsearch. So I need to these commands when the EC2 instance wakes up, and before the ES server is started: mkdir -p /mnt/elasticsearch chown elasticsearch.elasticsearch /mnt/elasticsearch Is there an easy way to do this from the /etc/init.d/elasticsearch script, before the process user is changed from root to elasticsearch, I wonder...? -- 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/87wqipewa1.fsf%40dod.no. For more options, visit https://groups.google.com/groups/opt_out.
