# Cross cluster search stops working after some time

**URL:** <https://discuss.elastic.co/t/cross-cluster-search-stops-working-after-some-time/107189>\
**Category:** Elasticsearch\
**Created:** [November 10, 2017, 1:06pm UTC](https://discuss.elastic.co/t/cross-cluster-search-stops-working-after-some-time/107189 "2017-11-10T13:06:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alberto\_Yoldi](https://avatars.discourse-cdn.com/v4/letter/a/b782af/32.png) [@Alberto\_Yoldi](https://discuss.elastic.co/u/Alberto_Yoldi)\
**Post date:** [November 10, 2017, 1:06pm UTC](https://discuss.elastic.co/t/cross-cluster-search-stops-working-after-some-time/107189/1 "2017-11-10T13:06:51Z")

</div>

I got cross cluster search working but after some time it simply breaks without any log entry (neither on the local cluster nor on the remote one). It happens the following:

- The remote cluster is already running since days.
- I start the local cluster and the cross cluster search simply works. Reliable and fast.
- I wait some time (1 or 2 hours) and perform again the same cross cluster search and it simply hangs until the timeout is reached. Then the following message is printed on the local cluster logfiles:

[2017-11-10T14:04:29,127][WARN][r.suppressed] path: /:/\_search, params: {q=\*, index=:}  
org.elasticsearch.transport.TransportException: unable to communicate with remote cluster []  
at org.elasticsearch.transport.RemoteClusterService$1.onFailure(RemoteClusterService.java:244) ~[elasticsearch-5.6.4.jar:5.6.4]  
at org.elasticsearch.transport.RemoteClusterConnection$1.handleException(RemoteClusterConnection.java:188) ~[elasticsearch-5.6.4.jar:5.6.4]  
at org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler.handleException(TransportService.java:1077) ~[elasticsearch-5.6.4.jar:5.6.4]  
at org.elasticsearch.transport.TransportService$Adapter.lambda$onConnectionClosed$6(TransportService.java:903) ~[elasticsearch-5.6.4.jar:5.6.4]  
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:569) [elasticsearch-5.6.4.jar:5.6.4]  
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0\_111]  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0\_111]  
at java.lang.Thread.run(Thread.java:745) [?:1.8.0\_111]  
Caused by: org.elasticsearch.transport.NodeDisconnectedException: [][:9300][indices:admin/shards/search\_shards] disconnected

Any clue of what can be going on?

Many thanks in advance!

---

<div class="post-metadata">

**Author:** ![Alberto\_Yoldi](https://avatars.discourse-cdn.com/v4/letter/a/b782af/32.png) [@Alberto\_Yoldi](https://discuss.elastic.co/u/Alberto_Yoldi)\
**Post date:** [November 10, 2017, 1:10pm UTC](https://discuss.elastic.co/t/cross-cluster-search-stops-working-after-some-time/107189/2 "2017-11-10T13:10:32Z")

</div>

Looks like the same behavior was already reported on September:

> [@Random time out in cross-cluster seach Kibana (5.5)](https://discuss.elastic.co/t/random-time-out-in-cross-cluster-seach-kibana-5-5/100337):
>
> Hello, I am trying to do a PoC using cross-cluster search in Kibana. My problem is that from time to time (for what I can see is random), I get timeouts in kibana when working with index from a cross-cluster search. So to sum up what I have: Kibana timeots are just happening when cross-clustering search. During the timeouts I can change the index to a local one and kibana show results. After a minute or so, the connection get restored (without any action on my part). It is not a firewall p…

---

<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:** [December 8, 2017, 1:10pm UTC](https://discuss.elastic.co/t/cross-cluster-search-stops-working-after-some-time/107189/3 "2017-12-08T13:10:37Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.