# Remote cluster not displayed but acknowledged

**URL:** <https://discuss.elastic.co/t/remote-cluster-not-displayed-but-acknowledged/269992>\
**Category:** Elasticsearch\
**Tags:** ccr-cross-cluster-replication\
**Created:** [April 13, 2021, 10:45am UTC](https://discuss.elastic.co/t/remote-cluster-not-displayed-but-acknowledged/269992 "2021-04-13T10:45:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pavel.entner](https://avatars.discourse-cdn.com/v4/letter/p/d6d6ee/32.png) [@pavel.entner](https://discuss.elastic.co/u/pavel.entner)\
**Post date:** [April 13, 2021, 10:45am UTC](https://discuss.elastic.co/t/remote-cluster-not-displayed-but-acknowledged/269992/1 "2021-04-13T10:45:15Z")

</div>

Hello,

I'm quite new to Elasticsearch. I have installed two Elasticsearch clusters consisting of 3x master node and 3x data node each. On one master node on each cluster I'm running Kibana. I'm using https and transport ssl (both default ports 9200 & 9300).

I have activated trial license before customer will provide platinum one to be able to enable cross-cluster replication. However when I try to add new remote-cluster in Kibana (using 3x master nodes of the remote cluster as seeds), there is no error when saving it, but also no remote cluster is displayed in Stack Management -\> Remote Cluster. When I try to do the same via PUT \_cluster/settings request, it gets acknowledged without error. But when I try to check remote cluster via GET \_remote/info?pretty, I'm getting empty brackets { }, so similar behaviour like in Kibana. Both clusters are using the same root CA certificate.

Example of elasticsearch.yml used on one of the follower cluster master nodes (same config used across both clusters except node roles):

> cluster.name: elasticsearch\_follower\_cluster  
> node.name: hostname31\_master  
> node.master: true  
> node.data: false  
> node.ingest: false  
> node.ml: False  
> xpack.ml.enabled: False  
> cluster.remote.connect: False  
> path.data: /data/elasticsearch  
> path.logs: /data/logs/elasticsearch  
> bootstrap.memory\_lock: True  
> network.host: x.x.x.118  
> http.port: 9200  
> discovery.seed\_hosts: ['x.x.x.117', 'x.x.x.118', 'x.x.x.119']  
> cluster.initial\_master\_nodes: ['hostname36\_master', 'hostname31\_master', 'hostname32\_master']  
> action.auto\_create\_index: .monitoring\*,.watches,.triggered\_watches,.watcher-history\*,.ml\*  
> xpack.security.enabled: true  
> xpack.security.http.ssl.enabled: true  
> xpack.security.http.ssl.keystore.path: /data/apps/elasticsearch/config/certs/hostname20\_master.p12  
> xpack.security.http.ssl.truststore.path: /data/apps/elasticsearch/config/certs/ca.p12  
> xpack.security.transport.ssl.enabled: true  
> xpack.security.transport.ssl.verification\_mode: certificate  
> xpack.security.transport.ssl.keystore.path: /data/apps/elasticsearch/config/certs/hostname20\_master.p12  
> xpack.security.transport.ssl.truststore.path: /data/apps/elasticsearch/config/certs/ca.p12

Example of my add remote cluster request:

> PUT \_cluster/settings  
> {  
> "persistent": {  
> "cluster": {  
> "remote": {  
> "elasticsearch\_leader\_cluster": {  
> "skip\_unavailable": false,  
> "mode": "sniff",  
> "proxy\_address": null,  
> "proxy\_socket\_connections": null,  
> "server\_name": null,  
> "seeds": [  
> "x.x.x.109:9300",  
> "x.x.x.113:9300",  
> "x.x.x.110:9300"  
> ],  
> "node\_connections": 3  
> }  
> }  
> }  
> }

Interesting thing is, that output of GET \_cluster/settings?include\_defaults=true&pretty is showing the remote cluster:

> elasticsearch@hostname31:~\> curl -X GET --cacert /etc/kibana/certs/ca.pem -u elastic "[https://x.x.x.118:9200/\_cluster/settings?include\_defaults=true&pretty](https://x.x.x.118:9200/_cluster/settings?include_defaults=true&pretty)"  
> Enter host password for user 'elastic':  
> {  
> "persistent" : {  
> "cluster" : {  
> "remote" : {  
> "elasticsearch\_leader\_cluster" : {  
> "mode" : "sniff",  
> "skip\_unavailable" : "false",  
> "node\_connections" : "3",  
> "seeds" : [  
> "x.x.x.109:9300",  
> "x.x.x.113:9300",  
> "x.x.x.110:9300"  
> ]

However GET \_remote/info is showing:

> elasticsearch@hostname31:~\> curl -X GET --cacert /etc/kibana/certs/ca.pem -u elastic "[https://x.x.x.118:9200/\_remote/info?pretty](https://x.x.x.118:9200/_remote/info?pretty)"  
> Enter host password for user 'elastic':  
> { }

And I'm getting these empty { } on both remote and local cluster.

Any ideas? Thank you very much for any suggestions.

---

<div class="post-metadata">

**Author:** ![pavel.entner](https://avatars.discourse-cdn.com/v4/letter/p/d6d6ee/32.png) [@pavel.entner](https://discuss.elastic.co/u/pavel.entner)\
**Post date:** [April 16, 2021, 8:35am UTC](https://discuss.elastic.co/t/remote-cluster-not-displayed-but-acknowledged/269992/2 "2021-04-16T08:35:38Z")

</div>

No ideas?

---

<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:** [May 14, 2021, 8:36am UTC](https://discuss.elastic.co/t/remote-cluster-not-displayed-but-acknowledged/269992/3 "2021-05-14T08:36:01Z")

</div>

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