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?
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?
On Fri, Jun 20, 2014 at 7:49 AM, Maciej Dziardziel fiedzia@gmail.com
wrote:
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?
On Friday, June 20, 2014 6:49:04 PM UTC+4, Maciej Dziardziel wrote:
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
Aha, thanks! - at my case pgrep is the most appropriate.
On Friday, June 20, 2014 6:49:04 PM UTC+4, Maciej Dziardziel wrote:
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
Aha, thanks! - at my case pgrep is the most appropriate.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.