Just a wild guess, but it seems that the /etc/init.d/elasticsearch restart command will, if properly named, stop a currently running instance and then start it.
If you issue the curl _shutdown command and then the restart command directly after without any delays, then perhaps that double blow from your sledgehammer is causing some corruption. In general, it's not good to mix HTTP REST (curl) commands and scripts that directly handle processes without adequate delays to ensure they aren't hammering on each other. Brian -- 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/d2679372-8184-4578-a9f6-a88dfe31ad42%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
