# \_remote/info?pretty cannot get the accurate/latest information

**URL:** <https://discuss.elastic.co/t/remote-info-pretty-cannot-get-the-accurate-latest-information/193418>\
**Category:** Elasticsearch\
**Tags:** ccs-cross-cluster-search\
**Created:** [August 1, 2019, 10:37pm UTC](https://discuss.elastic.co/t/remote-info-pretty-cannot-get-the-accurate-latest-information/193418 "2019-08-01T22:37:16Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![iShiBin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ishibin/32/32602_2.png) [@iShiBin](https://discuss.elastic.co/u/iShiBin)\
**Post date:** [August 1, 2019, 10:37pm UTC](https://discuss.elastic.co/t/remote-info-pretty-cannot-get-the-accurate-latest-information/193418/1 "2019-08-01T22:37:16Z")

</div>

After I set up the cross-cluster search and restarted the ES node, this API doesn't return empty seeds node until I make a cross-cluster search request.

Is it a bug? And how to address it?

Here is the empty feedback.

```json
{
    "seeds" : [],
    "http_addresses" : [],
    "connected" : false,
    "num_nodes_connected" : 0,
    "max_connections_per_cluster" : 3,
    "initial_connect_timeout" : "30s",
    "skip_unavailable" : true
  }

```

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [August 2, 2019, 8:16am UTC](https://discuss.elastic.co/t/remote-info-pretty-cannot-get-the-accurate-latest-information/193418/2 "2019-08-02T08:16:35Z")

</div>

which versions of Elasticsearch are involved in this?

---

<div class="post-metadata">

**Author:** ![iShiBin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ishibin/32/32602_2.png) [@iShiBin](https://discuss.elastic.co/u/iShiBin)\
**Post date:** [August 2, 2019, 9:42pm UTC](https://discuss.elastic.co/t/remote-info-pretty-cannot-get-the-accurate-latest-information/193418/3 "2019-08-02T21:42:00Z")

</div>

I am using 6.2. And I've head there is some fix on 6.6 by introducing a new setting: [https://github.com/elastic/elasticsearch/pull/34753](https://github.com/elastic/elasticsearch/pull/34753)

Right?

---

<div class="post-metadata">

**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:** [August 6, 2019, 8:08am UTC](https://discuss.elastic.co/t/remote-info-pretty-cannot-get-the-accurate-latest-information/193418/4 "2019-08-06T08:08:16Z")

</div>

Hi,  
do you configure CCS in elasticsearch.yml or via cluster update settings API?

---

<div class="post-metadata">

**Author:** ![iShiBin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ishibin/32/32602_2.png) [@iShiBin](https://discuss.elastic.co/u/iShiBin)\
**Post date:** [August 10, 2019, 5:58am UTC](https://discuss.elastic.co/t/remote-info-pretty-cannot-get-the-accurate-latest-information/193418/5 "2019-08-10T05:58:56Z")

</div>

REST API

---

<div class="post-metadata">

**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:** [August 12, 2019, 8:48am UTC](https://discuss.elastic.co/t/remote-info-pretty-cannot-get-the-accurate-latest-information/193418/6 "2019-08-12T08:48:04Z")

</div>

Restarting nodes should not be necessary. As long as you wait for the response of the cluster update settings API to come back, the connection to the remote clusters should initiated. What do you get back from the cluster update settings API?

---

<div class="post-metadata">

**Author:** ![iShiBin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ishibin/32/32602_2.png) [@iShiBin](https://discuss.elastic.co/u/iShiBin)\
**Post date:** [August 14, 2019, 4:34am UTC](https://discuss.elastic.co/t/remote-info-pretty-cannot-get-the-accurate-latest-information/193418/7 "2019-08-14T04:34:20Z")

</div>

The cluster setting update is sccessful because I get `{ackownledged: true}` response.

---

<div class="post-metadata">

**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:** [August 15, 2019, 8:29am UTC](https://discuss.elastic.co/t/remote-info-pretty-cannot-get-the-accurate-latest-information/193418/8 "2019-08-15T08:29:31Z")

</div>

Ok, and can you reproduce this all the time? Meaning every time you register a new cluster, you call remote info API after cluster update settings API has returned, and you get no nodes connected, yet you run search, you get results and the nodes appear in the output of remote info?

I am asking because it may happen depending on your setup, I guess, but it's not the expected behaviour.

---

<div class="post-metadata">

**Author:** ![iShiBin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ishibin/32/32602_2.png) [@iShiBin](https://discuss.elastic.co/u/iShiBin)\
**Post date:** [August 16, 2019, 4:08am UTC](https://discuss.elastic.co/t/remote-info-pretty-cannot-get-the-accurate-latest-information/193418/9 "2019-08-16T04:08:50Z")

</div>

Yes. I can reproduce it.

---

<div class="post-metadata">

**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:** [August 16, 2019, 7:58am UTC](https://discuss.elastic.co/t/remote-info-pretty-cannot-get-the-accurate-latest-information/193418/10 "2019-08-16T07:58:42Z")

</div>

Could you say something more about your network layout?

---

<div class="post-metadata">

**Author:** ![iShiBin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ishibin/32/32602_2.png) [@iShiBin](https://discuss.elastic.co/u/iShiBin)\
**Post date:** [August 16, 2019, 8:45pm UTC](https://discuss.elastic.co/t/remote-info-pretty-cannot-get-the-accurate-latest-information/193418/11 "2019-08-16T20:45:29Z")

</div>

Two clusters are in the same local network. I have two physical servers running docker on containers over calico network.

---

<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:** [September 13, 2019, 8:45pm UTC](https://discuss.elastic.co/t/remote-info-pretty-cannot-get-the-accurate-latest-information/193418/12 "2019-09-13T20:45:52Z")

</div>

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