# Problems searching ES from other machine

**URL:** <https://discuss.elastic.co/t/problems-searching-es-from-other-machine/19712>\
**Category:** Elasticsearch\
**Created:** [September 10, 2014, 11:34am UTC](https://discuss.elastic.co/t/problems-searching-es-from-other-machine/19712 "2014-09-10T11:34:38Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andrew\_Lakes](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@Andrew\_Lakes](https://discuss.elastic.co/u/Andrew_Lakes)\
**Post date:** [September 10, 2014, 11:34am UTC](https://discuss.elastic.co/t/problems-searching-es-from-other-machine/19712/1 "2014-09-10T11:34:38Z")

</div>

Hey Guys,

today we encoutered a problem while requesting some data from our ES db  
from an other server in our network.

All that the other server does is executing the following request:

curl -XGET '[https://elasticsearch-server:443/logstash-2014.09.10,logstash-2014.09.09/\_search?pretty](https://elasticsearch-server:443/logstash-2014.09.10,logstash-2014.09.09/_search?pretty)' -d '{  
"query": {  
"filtered": {  
"query": {  
"bool": {  
"should": [  
{  
"query\_string": {  
"query": "field:\*"  
}  
}  
]  
}  
},  
"filter": {  
"bool": {  
"must": [  
{  
"range": {  
"@timestamp": {  
"from": 1410261816133,  
"to": 1410348216133  
}  
}  
},  
{  
"fquery": {  
"query": {  
"query\_string": {  
"query": "logsource:("servername")"  
}  
},  
"\_cache": true  
}  
}  
]  
}  
}  
}  
},  
"highlight": {  
"fields": {},  
"fragment\_size": 2147483647,  
"pre\_tags": [  
"@start-highlight@"  
],  
"post\_tags": [  
"@end-highlight@"  
]  
},  
"size": 100,  
"sort": [  
{  
"@timestamp": {  
"order": "desc",  
"ignore\_unmapped": true  
}  
},  
{  
"@timestamp": {  
"order": "desc",  
"ignore\_unmapped": true  
}  
}  
]  
}'

which simply count how much events 1 server over 24 hours got.

But if this request lead to some abnormal behavior of elasticsearch, we much of the following error messages in our es-log:

[2014-09-10 13:12:32,938][DEBUG][http.netty] [NodeName] Caught exception while handling client http traffic, closing connection [id: 0x5fd6fd9f, /:40784 :\> /\<IP of the ES server:9200]  
java.nio.channels.ClosedChannelException  
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.cleanUpWriteBuffer(AbstractNioWorker.java:433)  
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.writeFromUserCode(AbstractNioWorker.java:128)  
at org.elasticsearch.common.netty.channel.socket.nio.NioServerSocketPipelineSink.handleAcceptedSocket(NioServerSocketPipelineSink.java:99)  
at org.elasticsearch.common.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:36)  
at org.elasticsearch.common.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:779)  
at org.elasticsearch.common.netty.channel.Channels.write(Channels.java:725)  
at org.elasticsearch.common.netty.handler.codec.oneone.OneToOneEncoder.doEncode(OneToOneEncoder.java:71)  
at org.elasticsearch.common.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:59)  
at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)  
at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582)  
at org.elasticsearch.common.netty.channel.Channels.write(Channels.java:704)  
at org.elasticsearch.common.netty.channel.Channels.write(Channels.java:671)  
at org.elasticsearch.common.netty.channel.AbstractChannel.write(AbstractChannel.java:248)  
at org.elasticsearch.http.netty.NettyHttpChannel.sendResponse(NettyHttpChannel.java:173)  
at org.elasticsearch.rest.action.support.RestResponseListener.processResponse(RestResponseListener.java:43)  
at org.elasticsearch.rest.action.support.RestActionListener.onResponse(RestActionListener.java:49)  
at org.elasticsearch.action.search.type.TransportSearchQueryThenFetchAction$AsyncAction.innerFinishHim(TransportSearchQueryThenFetchAction.java:157)  
at org.elasticsearch.action.search.type.TransportSearchQueryThenFetchAction$AsyncAction.finishHim(TransportSearchQueryThenFetchAction.java:139)  
at org.elasticsearch.action.search.type.TransportSearchQueryThenFetchAction$AsyncAction.moveToSecondPhase(TransportSearchQueryThenFetchAction.java:90)  
at org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.innerMoveToSecondPhase(TransportSearchTypeAction.java:404)  
at org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.onFirstPhaseResult(TransportSearchTypeAction.java:198)  
at org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction$1.onResult(TransportSearchTypeAction.java:174)  
at org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction$1.onResult(TransportSearchTypeAction.java:171)  
at org.elasticsearch.search.action.SearchServiceTransportAction$23.run(SearchServiceTransportAction.java:526)  
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
at java.lang.Thread.run(Thread.java:745

As soon as we active this request from the remote server we get a whole lot of this error messages and everything in elasticsearch slows down pretty hard (Even Kibana request get stuck in the queue).

Anybody got an idea why this is happening?

Any feedback is appreciated.

Thanks

--  
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](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/85627251-b4be-4031-870a-2bd621d0973c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/85627251-b4be-4031-870a-2bd621d0973c%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [September 10, 2014, 12:03pm UTC](https://discuss.elastic.co/t/problems-searching-es-from-other-machine/19712/2 "2014-09-10T12:03:50Z")

</div>

The message tells that on port 9200, the HTTP message could not be  
understood. Do you send non-HTTP traffic to port 9200?

Jörg

On Wed, Sep 10, 2014 at 1:34 PM, Andrew Lakes [alakes501@gmail.com](mailto:alakes501@gmail.com) wrote:

> Hey Guys,
> 
> today we encoutered a problem while requesting some data from our ES db  
> from an other server in our network.
> 
> All that the other server does is executing the following request:
> 
> curl -XGET '[https://elasticsearch-server:443/logstash-2014.09.10,logstash-2014.09.09/\_search?pretty](https://elasticsearch-server:443/logstash-2014.09.10,logstash-2014.09.09/_search?pretty)' -d '{  
> "query": {  
> "filtered": {  
> "query": {  
> "bool": {  
> "should": [  
> {  
> "query\_string": {  
> "query": "field:\*"  
> }  
> }  
> ]  
> }  
> },  
> "filter": {  
> "bool": {  
> "must": [  
> {  
> "range": {  
> "@timestamp": {  
> "from": 1410261816133,  
> "to": 1410348216133  
> }  
> }  
> },  
> {  
> "fquery": {  
> "query": {  
> "query\_string": {  
> "query": "logsource:("servername")"  
> }  
> },  
> "\_cache": true  
> }  
> }  
> ]  
> }  
> }  
> }  
> },  
> "highlight": {  
> "fields": {},  
> "fragment\_size": 2147483647,  
> "pre\_tags": [  
> "@start-highlight@"  
> ],  
> "post\_tags": [  
> "@end-highlight@"  
> ]  
> },  
> "size": 100,  
> "sort": [  
> {  
> "@timestamp": {  
> "order": "desc",  
> "ignore\_unmapped": true  
> }  
> },  
> {  
> "@timestamp": {  
> "order": "desc",  
> "ignore\_unmapped": true  
> }  
> }  
> ]  
> }'
> 
> which simply count how much events 1 server over 24 hours got.
> 
> But if this request lead to some abnormal behavior of elasticsearch, we much of the following error messages in our es-log:
> 
> [2014-09-10 13:12:32,938][DEBUG][http.netty] [NodeName] Caught exception while handling client http traffic, closing connection [id: 0x5fd6fd9f, /:40784 :\> /\<IP of the ES server:9200]  
> java.nio.channels.ClosedChannelException  
> at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.cleanUpWriteBuffer(AbstractNioWorker.java:433)  
> at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.writeFromUserCode(AbstractNioWorker.java:128)  
> at org.elasticsearch.common.netty.channel.socket.nio.NioServerSocketPipelineSink.handleAcceptedSocket(NioServerSocketPipelineSink.java:99)  
> at org.elasticsearch.common.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:36)  
> at org.elasticsearch.common.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:779)  
> at org.elasticsearch.common.netty.channel.Channels.write(Channels.java:725)  
> at org.elasticsearch.common.netty.handler.codec.oneone.OneToOneEncoder.doEncode(OneToOneEncoder.java:71)  
> at org.elasticsearch.common.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:59)  
> at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)  
> at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582)  
> at org.elasticsearch.common.netty.channel.Channels.write(Channels.java:704)  
> at org.elasticsearch.common.netty.channel.Channels.write(Channels.java:671)  
> at org.elasticsearch.common.netty.channel.AbstractChannel.write(AbstractChannel.java:248)  
> at org.elasticsearch.http.netty.NettyHttpChannel.sendResponse(NettyHttpChannel.java:173)  
> at org.elasticsearch.rest.action.support.RestResponseListener.processResponse(RestResponseListener.java:43)  
> at org.elasticsearch.rest.action.support.RestActionListener.onResponse(RestActionListener.java:49)  
> at org.elasticsearch.action.search.type.TransportSearchQueryThenFetchAction$AsyncAction.innerFinishHim(TransportSearchQueryThenFetchAction.java:157)  
> at org.elasticsearch.action.search.type.TransportSearchQueryThenFetchAction$AsyncAction.finishHim(TransportSearchQueryThenFetchAction.java:139)  
> at org.elasticsearch.action.search.type.TransportSearchQueryThenFetchAction$AsyncAction.moveToSecondPhase(TransportSearchQueryThenFetchAction.java:90)  
> at org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.innerMoveToSecondPhase(TransportSearchTypeAction.java:404)  
> at org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.onFirstPhaseResult(TransportSearchTypeAction.java:198)  
> at org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction$1.onResult(TransportSearchTypeAction.java:174)  
> at org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction$1.onResult(TransportSearchTypeAction.java:171)  
> at org.elasticsearch.search.action.SearchServiceTransportAction$23.run(SearchServiceTransportAction.java:526)  
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)  
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
> at java.lang.Thread.run(Thread.java:745
> 
> As soon as we active this request from the remote server we get a whole lot of this error messages and everything in elasticsearch slows down pretty hard (Even Kibana request get stuck in the queue).
> 
> Anybody got an idea why this is happening?
> 
> Any feedback is appreciated.
> 
> Thanks
> 
> --  
> 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](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/85627251-b4be-4031-870a-2bd621d0973c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/85627251-b4be-4031-870a-2bd621d0973c%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/85627251-b4be-4031-870a-2bd621d0973c%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/85627251-b4be-4031-870a-2bd621d0973c%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGLQUsiTq6WktoLDUTQ0\_WcU1ys\_uBEy21g6grmkAcPhg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGLQUsiTq6WktoLDUTQ0_WcU1ys_uBEy21g6grmkAcPhg%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Andrew\_Lakes](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@Andrew\_Lakes](https://discuss.elastic.co/u/Andrew_Lakes)\
**Post date:** [September 10, 2014, 2:00pm UTC](https://discuss.elastic.co/t/problems-searching-es-from-other-machine/19712/3 "2014-09-10T14:00:34Z")

</div>

Hi,

thx for response.

The remote server just do this request:

curl -XGET -s  
'[http://elasticsearch-server:9200/logstash-2014.09.10,logstash-2014.09.09/\_search?pretty](http://elasticsearch-server:9200/logstash-2014.09.10,logstash-2014.09.09/_search?pretty)'  
-d '{  
"facets": {  
"terms": {  
"terms": {  
"field": "\_type",  
"size": 10,  
"order": "count",  
"exclude":   
},  
"facet\_filter": {  
"fquery": {  
"query": {  
"filtered": {  
"query": {  
"bool": {  
"should": [  
{  
"query\_string": {  
"query": "field:\*"  
}  
}  
]  
}  
},  
"filter": {  
"bool": {  
"must": [  
{  
"range": {  
"@timestamp": {  
"from": "1410271471958",  
"to": "now"  
}  
}  
},  
{  
"fquery": {  
"query": {  
"query\_string": {  
"query": "logsource:("Servername")"  
}  
},  
"\_cache": true  
}  
}  
]  
}  
}  
}  
}  
}  
}  
}  
},  
"size": 0  
}'

and this curl-request looks like an http request - doesnt it?

Thanks.

Am Mittwoch, 10. September 2014 14:04:10 UTC+2 schrieb Jörg Prante:

> The message tells that on port 9200, the HTTP message could not be  
> understood. Do you send non-HTTP traffic to port 9200?
> 
> Jörg
> 
> On Wed, Sep 10, 2014 at 1:34 PM, Andrew Lakes \<[alak...@gmail.com](mailto:alak...@gmail.com)  
> \<javascript:\>\> wrote:
> 
> > Hey Guys,
> > 
> > today we encoutered a problem while requesting some data from our ES db  
> > from an other server in our network.
> > 
> > All that the other server does is executing the following request:
> > 
> > curl -XGET '[https://elasticsearch-server:443/logstash-2014.09.10,logstash-2014.09.09/\_search?pretty](https://elasticsearch-server:443/logstash-2014.09.10,logstash-2014.09.09/_search?pretty)' -d '{  
> > "query": {  
> > "filtered": {  
> > "query": {  
> > "bool": {  
> > "should": [  
> > {  
> > "query\_string": {  
> > "query": "field:\*"  
> > }  
> > }  
> > ]  
> > }  
> > },  
> > "filter": {  
> > "bool": {  
> > "must": [  
> > {  
> > "range": {  
> > "@timestamp": {  
> > "from": 1410261816133,  
> > "to": 1410348216133  
> > }  
> > }  
> > },  
> > {  
> > "fquery": {  
> > "query": {  
> > "query\_string": {  
> > "query": "logsource:("servername")"  
> > }  
> > },  
> > "\_cache": true  
> > }  
> > }  
> > ]  
> > }  
> > }  
> > }  
> > },  
> > "highlight": {  
> > "fields": {},  
> > "fragment\_size": 2147483647,  
> > "pre\_tags": [  
> > "@start-highlight@"  
> > ],  
> > "post\_tags": [  
> > "@end-highlight@"  
> > ]  
> > },  
> > "size": 100,  
> > "sort": [  
> > {  
> > "@timestamp": {  
> > "order": "desc",  
> > "ignore\_unmapped": true  
> > }  
> > },  
> > {  
> > "@timestamp": {  
> > "order": "desc",  
> > "ignore\_unmapped": true  
> > }  
> > }  
> > ]  
> > }'
> > 
> > which simply count how much events 1 server over 24 hours got.
> > 
> > But if this request lead to some abnormal behavior of elasticsearch, we much of the following error messages in our es-log:
> > 
> > [2014-09-10 13:12:32,938][DEBUG][http.netty] [NodeName] Caught exception while handling client http traffic, closing connection [id: 0x5fd6fd9f, /:40784 :\> /\<IP of the ES server:9200]  
> > java.nio.channels.ClosedChannelException  
> > at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.cleanUpWriteBuffer(AbstractNioWorker.java:433)  
> > at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.writeFromUserCode(AbstractNioWorker.java:128)  
> > at org.elasticsearch.common.netty.channel.socket.nio.NioServerSocketPipelineSink.handleAcceptedSocket(NioServerSocketPipelineSink.java:99)  
> > at org.elasticsearch.common.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:36)  
> > at org.elasticsearch.common.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:779)  
> > at org.elasticsearch.common.netty.channel.Channels.write(Channels.java:725)  
> > at org.elasticsearch.common.netty.handler.codec.oneone.OneToOneEncoder.doEncode(OneToOneEncoder.java:71)  
> > at org.elasticsearch.common.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:59)  
> > at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)  
> > at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582)  
> > at org.elasticsearch.common.netty.channel.Channels.write(Channels.java:704)  
> > at org.elasticsearch.common.netty.channel.Channels.write(Channels.java:671)  
> > at org.elasticsearch.common.netty.channel.AbstractChannel.write(AbstractChannel.java:248)  
> > at org.elasticsearch.http.netty.NettyHttpChannel.sendResponse(NettyHttpChannel.java:173)  
> > at org.elasticsearch.rest.action.support.RestResponseListener.processResponse(RestResponseListener.java:43)  
> > at org.elasticsearch.rest.action.support.RestActionListener.onResponse(RestActionListener.java:49)  
> > at org.elasticsearch.action.search.type.TransportSearchQueryThenFetchAction$AsyncAction.innerFinishHim(TransportSearchQueryThenFetchAction.java:157)  
> > at org.elasticsearch.action.search.type.TransportSearchQueryThenFetchAction$AsyncAction.finishHim(TransportSearchQueryThenFetchAction.java:139)  
> > at org.elasticsearch.action.search.type.TransportSearchQueryThenFetchAction$AsyncAction.moveToSecondPhase(TransportSearchQueryThenFetchAction.java:90)  
> > at org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.innerMoveToSecondPhase(TransportSearchTypeAction.java:404)  
> > at org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.onFirstPhaseResult(TransportSearchTypeAction.java:198)  
> > at org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction$1.onResult(TransportSearchTypeAction.java:174)  
> > at org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction$1.onResult(TransportSearchTypeAction.java:171)  
> > at org.elasticsearch.search.action.SearchServiceTransportAction$23.run(SearchServiceTransportAction.java:526)  
> > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)  
> > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
> > at java.lang.Thread.run(Thread.java:745
> > 
> > As soon as we active this request from the remote server we get a whole lot of this error messages and everything in elasticsearch slows down pretty hard (Even Kibana request get stuck in the queue).
> > 
> > Anybody got an idea why this is happening?
> > 
> > Any feedback is appreciated.
> > 
> > Thanks
> > 
> > --  
> > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/85627251-b4be-4031-870a-2bd621d0973c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/85627251-b4be-4031-870a-2bd621d0973c%40googlegroups.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/85627251-b4be-4031-870a-2bd621d0973c%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/85627251-b4be-4031-870a-2bd621d0973c%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > .  
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/62142975-1fb3-4294-bdf9-c09585dd7067%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/62142975-1fb3-4294-bdf9-c09585dd7067%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 1:03am UTC](https://discuss.elastic.co/t/problems-searching-es-from-other-machine/19712/4 "2017-07-06T01:03:18Z")

</div>