# Cluster (connect 2 nodes)

**URL:** <https://discuss.elastic.co/t/cluster-connect-2-nodes/134384>\
**Category:** Elasticsearch\
**Created:** [June 4, 2018, 8:11am UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384 "2018-06-04T08:11:35Z")\
**Posts on this page:** 13\
**Page:** 3

<div class="post-metadata">

**Author:** ![asalma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asalma/32/32199_2.png) [@asalma](https://discuss.elastic.co/u/asalma)\
**Post date:** [June 4, 2018, 12:29pm UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/41 "2018-06-04T12:29:09Z")

</div>

Yes it is still running :

```auto
[root@frghcslnetv12 ~]# systemctl status elasticsearch.service
● elasticsearch.service - Elasticsearch
   Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2018-06-04 13:32:55 CEST; 55min ago
     Docs: http://www.elastic.co
 Main PID: 52356 (java)
    Tasks: 70
   CGroup: /system.slice/elasticsearch.service
           └─52356 /bin/java -Xms1g -Xmx1g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+AlwaysPreTouch -Xss1m -Djava....

Jun 04 13:32:55 frghcslnetv12 systemd[1]: Started Elasticsearch.
Jun 04 13:32:55 frghcslnetv12 systemd[1]: Starting Elasticsearch...
[root@frghcslnetv12 ~]#

```

---

<div class="post-metadata">

**Author:** ![jamesspi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jamesspi/32/24479_2.png) [@jamesspi](https://discuss.elastic.co/u/jamesspi)\
**Post date:** [June 4, 2018, 12:32pm UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/42 "2018-06-04T12:32:49Z")

</div>

Can you show me your Kibana configuration please?

---

<div class="post-metadata">

**Author:** ![asalma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asalma/32/32199_2.png) [@asalma](https://discuss.elastic.co/u/asalma)\
**Post date:** [June 4, 2018, 12:34pm UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/43 "2018-06-04T12:34:45Z")

</div>

```auto
# Kibana is served by a back end server. This setting specifies the port to use.
#server.port: 5601

# Specifies the address to which the Kibana server will bind. IP addresses and host names are both valid values.
# The default is 'localhost', which usually means remote machines will not be able to connect.
# To allow connections from remote users, set this parameter to a non-loopback address.
#server.host: "localhost"

# Enables you to specify a path to mount Kibana at if you are running behind a proxy. This only affects
# the URLs generated by Kibana, your proxy is expected to remove the basePath value before forwarding requests
# to Kibana. This setting cannot end in a slash.
#server.basePath: ""

# The maximum payload size in bytes for incoming server requests.
#server.maxPayloadBytes: 1048576

# The Kibana server's name. This is used for display purposes.
#server.name: "your-hostname"

# The URL of the Elasticsearch instance to use for all your queries.
#elasticsearch.url: "http://localhost:9200"

# When this setting's value is true Kibana uses the hostname specified in the server.host
# setting. When the value of this setting is false, Kibana uses the hostname of the host
# that connects to this Kibana instance.
#elasticsearch.preserveHost: true

# Kibana uses an index in Elasticsearch to store saved searches, visualizations and
# dashboards. Kibana creates a new index if the index doesn't already exist.
#kibana.index: ".kibana"

# The default application to load.
#kibana.defaultAppId: "home"

# If your Elasticsearch is protected with basic authentication, these settings provide
# the username and password that the Kibana server uses to perform maintenance on the Kibana
# index at startup. Your Kibana users still need to authenticate with Elasticsearch, which
# is proxied through the Kibana server.
#elasticsearch.username: "user"
#elasticsearch.password: "pass"

# Enables SSL and paths to the PEM-format SSL certificate and SSL key files, respectively.
# These settings enable SSL for outgoing requests from the Kibana server to the browser.
#server.ssl.enabled: false
#server.ssl.certificate: /path/to/your/server.crt
#server.ssl.key: /path/to/your/server.key
# Optional settings that provide the paths to the PEM-format SSL certificate and key files.
# These files validate that your Elasticsearch backend uses the same key files.
#elasticsearch.ssl.certificate: /path/to/your/client.crt
#elasticsearch.ssl.key: /path/to/your/client.key

# Optional setting that enables you to specify a path to the PEM file for the certificate
# authority for your Elasticsearch instance.
#elasticsearch.ssl.certificateAuthorities: ["/path/to/your/CA.pem"]

# To disregard the validity of SSL certificates, change this setting's value to 'none'.
#elasticsearch.ssl.verificationMode: full

# Time in milliseconds to wait for Elasticsearch to respond to pings. Defaults to the value of
# the elasticsearch.requestTimeout setting.
#elasticsearch.pingTimeout: 1500

# Time in milliseconds to wait for responses from the back end or Elasticsearch. This value
# must be a positive integer.
#elasticsearch.requestTimeout: 30000

# List of Kibana client-side headers to send to Elasticsearch. To send *no* client-side
# headers, set this value to [] (an empty list).
#elasticsearch.requestHeadersWhitelist: [authorization]
# Header names and values that are sent to Elasticsearch. Any custom headers cannot be overwritten
# by client-side headers, regardless of the elasticsearch.requestHeadersWhitelist configuration.
#elasticsearch.customHeaders: {}

# Time in milliseconds for Elasticsearch to wait for responses from shards. Set to 0 to disable.
#elasticsearch.shardTimeout: 0

# Time in milliseconds to wait for Elasticsearch at Kibana startup before retrying.
#elasticsearch.startupTimeout: 5000

# Specifies the path where Kibana creates the process ID file.
#pid.file: /var/run/kibana.pid

# Enables you specify a file where Kibana stores log output.
#logging.dest: stdout

# Set the value of this setting to true to suppress all logging output.
#logging.silent: false

# Set the value of this setting to true to suppress all logging output other than error messages.
#logging.quiet: false

# Set the value of this setting to true to log all events, including system usage information
# and all requests.
#logging.verbose: false

# Set the interval in milliseconds to sample system and process performance
# metrics. Minimum is 100ms. Defaults to 5000.
#ops.interval: 5000

# The default locale. This locale can be used in certain circumstances to substitute any missing
# translations.
#i18n.defaultLocale: "en"
```

---

<div class="post-metadata">

**Author:** ![jamesspi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jamesspi/32/24479_2.png) [@jamesspi](https://discuss.elastic.co/u/jamesspi)\
**Post date:** [June 4, 2018, 12:36pm UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/44 "2018-06-04T12:36:45Z")

</div>

Ok, can you just re confirm the output of:

```
curl http://localhost:9200/_cat/nodes?pretty on .29?
```

---

<div class="post-metadata">

**Author:** ![asalma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asalma/32/32199_2.png) [@asalma](https://discuss.elastic.co/u/asalma)\
**Post date:** [June 4, 2018, 12:37pm UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/45 "2018-06-04T12:37:25Z")

</div>

> [@jamesspi](#):
>
> curl [http://localhost:9200/\_cat/nodes?pretty](http://localhost:9200/_cat/nodes?pretty)

```auto
[root@frghcslnetv10 ~]# curl http://localhost:9200/_cat/nodes?pretty
172.16.250.29 57 98 98 9.29 8.29 7.48 mdi * network-1

```

---

<div class="post-metadata">

**Author:** ![jamesspi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jamesspi/32/24479_2.png) [@jamesspi](https://discuss.elastic.co/u/jamesspi)\
**Post date:** [June 4, 2018, 12:39pm UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/46 "2018-06-04T12:39:11Z")

</div>

Ok, let's try this.

In your elasticsearch configuration on .29, change

```
discovery.zen.ping.unicast.hosts: ["172.16.250.29"]

```

to

```
discovery.zen.ping.unicast.hosts: ["172.16.250.30"]

```

and restart elasticsearch

Leave the .30 configuration as it is.

---

<div class="post-metadata">

**Author:** ![asalma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asalma/32/32199_2.png) [@asalma](https://discuss.elastic.co/u/asalma)\
**Post date:** [June 4, 2018, 12:42pm UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/47 "2018-06-04T12:42:00Z")

</div>

```auto
[root@frghcslnetv10 ~]# curl http://localhost:9200/_cat/nodes?pretty
172.16.250.30 60 27 0 0.00 0.01 0.12 mdi * network-2
172.16.250.29 36 67 50 6.93 7.96 7.55 mdi - network-1

```

![image](https://us1.discourse-cdn.com/elastic/original/3X/a/f/af043904004fd12a3e2b8b512031354871918333.png)

Is it working now ?

---

<div class="post-metadata">

**Author:** ![jamesspi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jamesspi/32/24479_2.png) [@jamesspi](https://discuss.elastic.co/u/jamesspi)\
**Post date:** [June 4, 2018, 12:43pm UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/48 "2018-06-04T12:43:25Z")

</div>

Yes, all good 🙂

---

<div class="post-metadata">

**Author:** ![asalma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asalma/32/32199_2.png) [@asalma](https://discuss.elastic.co/u/asalma)\
**Post date:** [June 4, 2018, 12:44pm UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/49 "2018-06-04T12:44:15Z")

</div>

Thank you a looot again 😃

---

<div class="post-metadata">

**Author:** ![asalma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asalma/32/32199_2.png) [@asalma](https://discuss.elastic.co/u/asalma)\
**Post date:** [June 4, 2018, 1:19pm UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/50 "2018-06-04T13:19:41Z")

</div>

When I stop elasticsearch on ".30", I can see jst the node 1 but when I stop elasticsearch on ".29" and I change on Kibana.yml =\> elasticsearch.url : "[http://172.16.250.30:9200](http://172.16.250.30:9200)" , I see nothing.

Do I have to change the output logstash ?

My output now is :

```auto
output {
        elasticsearch {
                hosts => ["localhost:9200"]
                document_id => "%{fingerprint}"
        }
}

```

---

<div class="post-metadata">

**Author:** ![asalma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asalma/32/32199_2.png) [@asalma](https://discuss.elastic.co/u/asalma)\
**Post date:** [June 4, 2018, 2:56pm UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/51 "2018-06-04T14:56:27Z")

</div>

> [@jamesspi](#):
>
> Or, even better, install the free version of x-pack to get monitoring set up (you can monitor all aspects of the cluster visually, very very helpful

Can you give me the link to install the free version of x-pack monitoring ?

---

<div class="post-metadata">

**Author:** ![jamesspi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jamesspi/32/24479_2.png) [@jamesspi](https://discuss.elastic.co/u/jamesspi)\
**Post date:** [June 5, 2018, 8:28am UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/52 "2018-06-05T08:28:39Z")

</div>

On logstash, it's best to set both elastic nodes:

```
    output {
        elasticsearch {
                hosts => ["172.16.250.30:9200", "172.16.250.29:9200"]
                document_id => "%{fingerprint}"
        }
}

```

For x-pack, you can following this guide:

[https://www.elastic.co/guide/en/x-pack/current/installing-xpack.html](https://www.elastic.co/guide/en/x-pack/current/installing-xpack.html)

---

<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:** [July 3, 2018, 8:28am UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/53 "2018-07-03T08:28:40Z")

</div>

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

[Previous page](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384.md?page=2)