Hi. We have ElasticSearch set up to run as a Windows service. Almost every
time we stop or restart the service, we get "Error 109: The pipe has been
ended". We're not sure if it comes from the Java runtime or from
ElasticSearch itself. It happens whether we stop or restart through
Services (services.msc) or programmatically (through Powershell script). I
have searched for a solution; I found nothing specific to ElasticSearch,
but I did find an indication that MongoDB had something similar in a
previous version (2.0.4, bug reports herehttps://jira.mongodb.org/browse/SERVER-1434
and here https://jira.mongodb.org/browse/SERVER-2833), and that perhaps
it is related to a Java application calling Thread.exit(0);. Perhaps we're
not shutting down ElasticSearch in quite the right way?
I don't know whether this has been seen before, so I thought I'd ask here
before raising a bug.
- Chris M.
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@example.com.
For more options, visit https://groups.google.com/groups/opt_out.