use start-stop-daemon or adapt /etc/init.d/elasticsearch to set up pidfile guarding es instance. Or just run this way: pgrep -f elasticsearch || ./start_es.sh
On Friday, June 20, 2014 3:21:08 PM UTC+1, Andrew Gaydenko wrote: > > There were a couple of times during development workflow I have started ES > script the second time. It results in red status (I use Elastic HQ) and > not-working. So I'm forced to regenerate all indexes (with all test data) > again. It takes noticeable time. > > At the moment I use this script > > ES_MAX_MEM="512M" > export ES_MAX_MEM > cd /ES-dir/bin > ./elasticsearch.in.sh > ./elasticsearch -f & > > > under Linux to start ES. Can you. please, suggest a trick to avoid falling > in red? > > -- 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/d78daaaf-305b-45b4-ad9a-e34cf1adbb22%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
