# Cross Cluster Search gives strange results when remote nodes become unavailable **URL:** \ **Category:** Elasticsearch\ **Created:** [December 5, 2018, 10:44pm UTC](https://discuss.elastic.co/t/cross-cluster-search-gives-strange-results-when-remote-nodes-become-unavailable/159616 "2018-12-05T22:44:27Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![javanna](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javanna/32/4698_2.png) [@javanna](https://discuss.elastic.co/u/javanna)\ **Post date:** [December 7, 2018, 2:02pm UTC](https://discuss.elastic.co/t/cross-cluster-search-gives-strange-results-when-remote-nodes-become-unavailable/159616/2 "2018-12-07T14:02:57Z")
Hi Maxim, see [Elasticsearch CCS: client get timeout when remote cluster is isolated by firewall](https://discuss.elastic.co/t/elasticsearch-ccs-client-get-timeout-when-remote-cluster-is-isolated-by-firewall/152019/8) for a similar recent discussion. Elasticsearch is currently not super quick detecting when remote clusters are down and that may make requests hang. We have been working on improving that and some changes in that direction will go out with the 6.6 version. One thing you could do on your end is tweak OS settings like suggested by David in the linked discussion, see also [https://github.com/elastic/elasticsearch/issues/34405#issuecomment-429465972](https://github.com/elastic/elasticsearch/issues/34405#issuecomment-429465972) . Cheers Luca --- _[View the full topic](https://discuss.elastic.co/t/cross-cluster-search-gives-strange-results-when-remote-nodes-become-unavailable/159616)._