Hi all,
So I have an ES cluster that is currently exhibiting the following
properties:
If I do:
curl -k -vv http://elasticsearch.example.com:9200/logstash*/_search
The request returns properly with the expected results (I get a 200 OK
with the search results).
If I do:
curl -k -vv http://elasticsearch.example.com:9200/logstash*/_search?pretty
I get:
- Recv failure: Connection reset by peer
- Closing connection 0
curl: (56) Recv failure: Connection reset by peer
If I do:
curl -k -vv http://elasticsearch.example.com:9200/logstash*/_search/?pretty
The request also returns normally (a 200 OK)
If I do either of these from one of the machines in the cluster, all of
them work.
So it seems to be network interference somewhere. My question is, has
anybody seen Elasticsearch do this, and if so, what was the resolution?
If not, does anybody have any tips as to how I might track this down? Also
this is newer behaviour within the past week or so, which is also odd.
Thanks,
Ian
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/4f4e6bfe-2ab0-4c38-9709-55ad440b941f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.