# Cross Cluster Search locally

**URL:** https://discuss.elastic.co/t/cross-cluster-search-locally/215373
**Category:** Elastic Training
**Tags:** ccs-cross-cluster-search
**Created:** [January 16, 2020, 6:29pm UTC](https://discuss.elastic.co/t/cross-cluster-search-locally/215373 "2020-01-16T18:29:13Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Mack\_rogers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mack_rogers/32/53224_2.png) [@Mack\_rogers](https://discuss.elastic.co/u/Mack_rogers)
#### Post date: [January 16, 2020, 6:29pm UTC](https://discuss.elastic.co/t/cross-cluster-search-locally/215373/1 "2020-01-16T18:29:13Z")

</div>

Does anyone know how to set up cross-cluster search on a locally using a zip version of Elasticsearch search? Whatever mixture of nodes between 2 clusters, how do you get cluster 1 to talk to cluster 2.

My current yml settings are as followed.  
cluster.name: cluster 1  
xpack.security.enabled: true  
xpack.security.transport.ssl.enabled: true  
xpack.security.transport.ssl.verification\_mode: certificate  
xpack.security.transport.ssl.keystore.path: elastic-certificates.p12  
xpack.security.transport.ssl.truststore.path: elastic-certificates.p12

I opened this same terminal and created a 5-node cluster.  
node.name=node1  
node.name=node2  
node.name=node3  
node.name=node4  
node.name=node5

Another complete install of elasticsearch installed and open with these yml settings. No security enabled as it looking for the cluster1 keystore.

cluster.name=cluster2  
node.name=node6

After starting all terminals I receive the following errors from the cluster1 nodes

[node1] fetching nodes from external cluster [my\_application] failed

---

<div class="post-metadata">

### Author: ![Elvis\_Saravia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/elvis_saravia/32/45624_2.png) [@Elvis\_Saravia](https://discuss.elastic.co/u/Elvis_Saravia)
#### Post date: [January 16, 2020, 8:02pm UTC](https://discuss.elastic.co/t/cross-cluster-search-locally/215373/2 "2020-01-16T20:02:07Z")

</div>

Hi @Mack_rogers,

Thanks a lot for taking the time to open this discussion. We will probably need a bit more information from your setup and request to give you an educated and proper answer. Can you please copy and paste the cross-cluster search request you are performing here in the discussion? And let's see if we can figure out things from there.

Awaiting your response.

---

<div class="post-metadata">

### Author: ![Mack\_rogers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mack_rogers/32/53224_2.png) [@Mack\_rogers](https://discuss.elastic.co/u/Mack_rogers)
#### Post date: [January 21, 2020, 3:46pm UTC](https://discuss.elastic.co/t/cross-cluster-search-locally/215373/3 "2020-01-21T15:46:36Z")

</div>

Solved...this is my PUT command.

PUT \_cluster/settings  
{  
"persistent": {  
"cluster": {  
"remote": {  
"cluster1": {  
"seeds": [  
"127.0.0.1:9300"  
],  
"transport.ping\_schedule": "30s"  
},  
"cluster2": {  
"seeds": [  
"127.0.0.1:9305"  
],  
"transport.compress": true,  
"skip\_unavailable": true  
}  
}  
}  
},  
"transient": {  
"cluster": {  
"routing": {  
"allocation.awareness.attributes": "my\_rack"  
}  
}  
}  
}

I then checked cluster/remote settings and both addresses are connected: true

I performed a this query and got back results GET cluster2:earthquakes,earthquakes/\_search

The IP's were taken from the published addresses when the nodes start up. So I took the cluster1, node1 published address against the cluster2, node6 published address.

NO security is enabled for either cluster for this sample.

---

<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: [February 20, 2020, 3:46pm UTC](https://discuss.elastic.co/t/cross-cluster-search-locally/215373/4 "2020-02-20T15:46:43Z")

</div>

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