# Installed and configured ElasticSearch (Multi Node) Cluster on CentOS

**URL:** https://discuss.elastic.co/t/installed-and-configured-elasticsearch-multi-node-cluster-on-centos/33410
**Category:** Elasticsearch
**Created:** [October 30, 2015, 7:21pm UTC](https://discuss.elastic.co/t/installed-and-configured-elasticsearch-multi-node-cluster-on-centos/33410 "2015-10-30T19:21:41Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![ananthanaidu](https://avatars.discourse-cdn.com/v4/letter/a/f08c70/32.png) [@ananthanaidu](https://discuss.elastic.co/u/ananthanaidu)
#### Post date: [October 30, 2015, 7:21pm UTC](https://discuss.elastic.co/t/installed-and-configured-elasticsearch-multi-node-cluster-on-centos/33410/1 "2015-10-30T19:21:41Z")

</div>

Hello

Greetings,

I have two queries here,

**Query1:**

I have installed ELK with two nodes (node1,node2) and configured in elasticsearch.yml with the same cluster name on both nodes and host name as node1 and node2 respectively but the node2 is not replicating with node1.

My **Elastisearch.yml config**

Primary node1:  
cluster.name: “xxxLogs”  
node.name: "node1"  
node.master: True  
node.data: True  
network:”Host IP”

Secondary node2:  
cluster.name: “xxxLogs”  
node.name: "node2"  
node.master: True (if i comment it its working if this changed either to True or False kibana page was not loading for me)  
node.data: True  
network:”Host IP”

Is there any other steps to auto discover the node2 server into same cluster ?

Could you please help me to configure cluster and auto discover the node2 into the same cluster for replicating with node1.

**Query2:**

Please suggest if i configure index patterns its possible to achieve two different data with two nodes configured in same cluster both the data can be seen in kibana dashboard or any other way out there?

Thanks in Advance..

---

<div class="post-metadata">

### Author: ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [October 30, 2015, 8:27pm UTC](https://discuss.elastic.co/t/installed-and-configured-elasticsearch-multi-node-cluster-on-centos/33410/2 "2015-10-30T20:27:12Z")

</div>

> ```
> network:”Host IP”
> 
> ```

I'm not sure `network` is a valid configuration keyword.

Are you using multicast discovery? Have you looked in the logs of either machine? Are they able to find each other?

---

<div class="post-metadata">

### Author: ![ananthanaidu](https://avatars.discourse-cdn.com/v4/letter/a/f08c70/32.png) [@ananthanaidu](https://discuss.elastic.co/u/ananthanaidu)
#### Post date: [October 30, 2015, 8:45pm UTC](https://discuss.elastic.co/t/installed-and-configured-elasticsearch-multi-node-cluster-on-centos/33410/3 "2015-10-30T20:45:58Z")

</div>

network:"Host IP" i mean to say its my server ip address.

Iam not using muticast discovery and i checked the logs there is no replication between nodes.

can you throw some lights on steps how to find the each other in cluster?

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [October 31, 2015, 3:51am UTC](https://discuss.elastic.co/t/installed-and-configured-elasticsearch-multi-node-cluster-on-centos/33410/4 "2015-10-31T03:51:02Z")

</div>

What version did you install, because 2.0 doesn't do multicast anymore.

---

<div class="post-metadata">

### Author: ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [October 31, 2015, 11:00am UTC](https://discuss.elastic.co/t/installed-and-configured-elasticsearch-multi-node-cluster-on-centos/33410/5 "2015-10-31T11:00:43Z")

</div>

> Iam not using muticast discovery and i checked the logs there is no replication between nodes.

If you're using unicast discovery, what do the unicast configuration options in elasticsearch.yml look like? With unicast discovery nodes must be explicitly configured to find each other.

---

<div class="post-metadata">

### Author: ![ananthanaidu](https://avatars.discourse-cdn.com/v4/letter/a/f08c70/32.png) [@ananthanaidu](https://discuss.elastic.co/u/ananthanaidu)
#### Post date: [November 2, 2015, 5:36pm UTC](https://discuss.elastic.co/t/installed-and-configured-elasticsearch-multi-node-cluster-on-centos/33410/7 "2015-11-02T17:36:31Z")

</div>

Iam not using both multicast and unicast below is my elasticsearch.yml,

```
# Unicast discovery allows to explicitly control which nodes will be used
# to discover the cluster. It can be used when multicast is not present,
# or to restrict the cluster communication-wise.
#
# 1. Disable multicast discovery (enabled by default):
#
#discovery.zen.ping.multicast.enabled: false
#
# 2. Configure an initial list of master nodes in the cluster
# to perform discovery when new nodes (master or data) are started:
#
#discovery.zen.ping.unicast.hosts: ["host1", "host2:port"]
```

---

<div class="post-metadata">

### Author: ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [November 2, 2015, 6:23pm UTC](https://discuss.elastic.co/t/installed-and-configured-elasticsearch-multi-node-cluster-on-centos/33410/8 "2015-11-02T18:23:32Z")

</div>

For best results, please

- post non-comment lines from elasticsearch.yml (you can use `sed '/^#/d; /^$/d' /etc/elasticsearch/elasticsearch.yml` to collect them),
- format them as preformatted (Ctrl+K), and
- pay attention to the preview pane to the right.

---

<div class="post-metadata">

### Author: ![ananthanaidu](https://avatars.discourse-cdn.com/v4/letter/a/f08c70/32.png) [@ananthanaidu](https://discuss.elastic.co/u/ananthanaidu)
#### Post date: [November 2, 2015, 6:35pm UTC](https://discuss.elastic.co/t/installed-and-configured-elasticsearch-multi-node-cluster-on-centos/33410/9 "2015-11-02T18:35:47Z")

</div>

Thanks for your update, please find below non comment lines from elasticsearch.yml,

**Node1**  
cluster.name: ELKTEST  
node.name: "node1"  
network.host: 192.168.44.129

**Node2**  
cluster.name: ELKTEST  
node.name: "node2"  
network.host: 192.168.44.130

---

<div class="post-metadata">

### Author: ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [November 2, 2015, 6:39pm UTC](https://discuss.elastic.co/t/installed-and-configured-elasticsearch-multi-node-cluster-on-centos/33410/10 "2015-11-02T18:39:57Z")

</div>

Use unicast discovery as described here: [https://www.elastic.co/guide/en/elasticsearch/guide/current/\_important\_configuration\_changes.html#\_prefer\_unicast\_over\_multicast](https://www.elastic.co/guide/en/elasticsearch/guide/current/_important_configuration_changes.html#_prefer_unicast_over_multicast)

(And make sure each node has a unique node name. In your example above both are named node2.)

---

<div class="post-metadata">

### Author: ![ananthanaidu](https://avatars.discourse-cdn.com/v4/letter/a/f08c70/32.png) [@ananthanaidu](https://discuss.elastic.co/u/ananthanaidu)
#### Post date: [November 2, 2015, 6:41pm UTC](https://discuss.elastic.co/t/installed-and-configured-elasticsearch-multi-node-cluster-on-centos/33410/11 "2015-11-02T18:41:43Z")

</div>

thanks. sorry it was typo error its node1 and node2.

---

<div class="post-metadata">

### Author: ![ananthanaidu](https://avatars.discourse-cdn.com/v4/letter/a/f08c70/32.png) [@ananthanaidu](https://discuss.elastic.co/u/ananthanaidu)
#### Post date: [November 2, 2015, 11:48pm UTC](https://discuss.elastic.co/t/installed-and-configured-elasticsearch-multi-node-cluster-on-centos/33410/12 "2015-11-02T23:48:07Z")

</div>

We have done the below changes in the servers but unable to see the data sync.

cluster.name: ELKTEST  
node.name: "node2"  
network.host: 192.168.44.130  
discovery.zen.ping.multicast.enabled: false  
discovery.zen.ping.unicast.hosts: ["192.168.44.129", "192.168.44.130:9200"]

cluster.name: ELKTEST  
node.name: "node1"  
network.host: 192.168.44.129  
discovery.zen.ping.multicast.enabled: false  
discovery.zen.ping.unicast.hosts: ["192.168.44.129", "192.168.44.130:9200"]

---

<div class="post-metadata">

### Author: ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [November 3, 2015, 4:15am UTC](https://discuss.elastic.co/t/installed-and-configured-elasticsearch-multi-node-cluster-on-centos/33410/13 "2015-11-03T04:15:51Z")

</div>

Elasticsearch internally communicate on port 9300, not 9200 which is used for the REST interface.

---

<div class="post-metadata">

### Author: ![ananthanaidu](https://avatars.discourse-cdn.com/v4/letter/a/f08c70/32.png) [@ananthanaidu](https://discuss.elastic.co/u/ananthanaidu)
#### Post date: [November 3, 2015, 5:13pm UTC](https://discuss.elastic.co/t/installed-and-configured-elasticsearch-multi-node-cluster-on-centos/33410/14 "2015-11-03T17:13:51Z")

</div>

Still data is not syncing from master node(NODE1) data node(NODE2) after the below changes.

cluster.name: ELKTEST  
node.name: "node1"  
network.host: 192.168.44.129  
transport.tcp.port: 9300  
discovery.zen.ping.multicast.enabled: false  
discovery.zen.ping.unicast.hosts: ["192.168.44.129", "192.168.44.130:9300"]

cluster.name: ELKTEST  
node.name: "node2"  
network.host: 192.168.44.130  
transport.tcp.port: 9300  
discovery.zen.ping.multicast.enabled: false  
discovery.zen.ping.unicast.hosts: ["192.168.44.130", "192.168.44.129:9300"]

---

<div class="post-metadata">

### Author: ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [November 3, 2015, 5:55pm UTC](https://discuss.elastic.co/t/installed-and-configured-elasticsearch-multi-node-cluster-on-centos/33410/15 "2015-11-03T17:55:31Z")

</div>

What's in the logs? I'm sure there's _something_ discovery-related there.

---

<div class="post-metadata">

### Author: ![ananthanaidu](https://avatars.discourse-cdn.com/v4/letter/a/f08c70/32.png) [@ananthanaidu](https://discuss.elastic.co/u/ananthanaidu)
#### Post date: [November 3, 2015, 11:23pm UTC](https://discuss.elastic.co/t/installed-and-configured-elasticsearch-multi-node-cluster-on-centos/33410/16 "2015-11-03T23:23:04Z")

</div>

Thanks for your help.

With below configuration we are able to sync the data from master node(node1) to data node(node2)

cluster.name: ELKTEST  
node.name: "node2"  
network.host: 192.168.44.130  
transport.tcp.port: 9300  
discovery.zen.ping.unicast.hosts: ["192.168.44.130", "192.168.44.129:9300"]

cluster.name: ELKTEST  
node.name: "node1"  
network.host: 192.168.44.129  
transport.tcp.port: 9300  
discovery.zen.ping.unicast.hosts: ["192.168.44.129", "192.168.44.130:9300"]

---

<div class="post-metadata">

### Author: ![ananthanaidu](https://avatars.discourse-cdn.com/v4/letter/a/f08c70/32.png) [@ananthanaidu](https://discuss.elastic.co/u/ananthanaidu)
#### Post date: [November 3, 2015, 11:24pm UTC](https://discuss.elastic.co/t/installed-and-configured-elasticsearch-multi-node-cluster-on-centos/33410/17 "2015-11-03T23:24:21Z")

</div>

**Query1** is resolved.

Can you help us with below query2  
**Query2:**

Please suggest if i configure index patterns its possible to achieve two different data from different storages with two nodes configured in same cluster both the data can be seen in kibana dashboard or any other way out there?

Thanks in Advance..

---

<div class="post-metadata">

### Author: ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [November 4, 2015, 6:55am UTC](https://discuss.elastic.co/t/installed-and-configured-elasticsearch-multi-node-cluster-on-centos/33410/18 "2015-11-04T06:55:04Z")

</div>

> Please suggest if i configure index patterns its possible to achieve two different data from different storages with two nodes configured in same cluster both the data can be seen in kibana dashboard or any other way out there?

Sorry, I don't know what you're asking here. You want to control the mapping between indexes and the underlying storage?

---

<div class="post-metadata">

### Author: ![ananthanaidu](https://avatars.discourse-cdn.com/v4/letter/a/f08c70/32.png) [@ananthanaidu](https://discuss.elastic.co/u/ananthanaidu)
#### Post date: [November 4, 2015, 5:14pm UTC](https://discuss.elastic.co/t/installed-and-configured-elasticsearch-multi-node-cluster-on-centos/33410/19 "2015-11-04T17:14:34Z")

</div>

I have configured Node1 and Node2 servers both have different data can I see both node data in single search of Kibana dashboard.

**Node1 has New logs**  
**Node2 has Old logs**

if thats possible please provide me some steps to configure.

Thanks.

---

<div class="post-metadata">

### Author: ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [November 4, 2015, 6:16pm UTC](https://discuss.elastic.co/t/installed-and-configured-elasticsearch-multi-node-cluster-on-centos/33410/20 "2015-11-04T18:16:24Z")

</div>

I think we have one of these two situations:

- You've managed to get a split brain situation, i.e. you've basically forked your cluster. In a proper cluster there is only one set of indexes containing data and you can query any node and get the same results. Where the data is physically stored is irrelevant for clients making queries.
- Everything's fine and you're focusing too much on what data is stored on each node.

How did you reach the conclusion that node1 has new logs and node2 has old logs? Are you not able to access a unified view of the cluster by using the REST APIs?

---

<div class="post-metadata">

### Author: ![ananthanaidu](https://avatars.discourse-cdn.com/v4/letter/a/f08c70/32.png) [@ananthanaidu](https://discuss.elastic.co/u/ananthanaidu)
#### Post date: [November 4, 2015, 6:51pm UTC](https://discuss.elastic.co/t/installed-and-configured-elasticsearch-multi-node-cluster-on-centos/33410/21 "2015-11-04T18:51:02Z")

</div>

> [@magnusbaeck](#):
>
> Everything's fine and you're focusing too much on what data is stored on each node.

Yes am into this situation to store my data as below,

Node1 has New logs ( **Replica Stopped and imported New logs in Node1** )  
Node2 has Old logs

Is that possible to see both data in single search of kibana dashboard.

[Next page](https://discuss.elastic.co/t/installed-and-configured-elasticsearch-multi-node-cluster-on-centos/33410.md?page=2)
