# I can't add a new node to my cluster **URL:** \ **Category:** Elasticsearch\ **Created:** [June 23, 2020, 11:52am UTC](https://discuss.elastic.co/t/i-cant-add-a-new-node-to-my-cluster/238250 "2020-06-23T11:52:28Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![dferez](https://avatars.discourse-cdn.com/v4/letter/d/74df32/32.png) [@dferez](https://discuss.elastic.co/u/dferez)\ **Post date:** [June 23, 2020, 11:52am UTC](https://discuss.elastic.co/t/i-cant-add-a-new-node-to-my-cluster/238250/1 "2020-06-23T11:52:28Z")
Hi. I currently have a two node cluster, each node is separated on a different host. I want to add a third node to the cluster, but it does not start, it has never started. Next I leave the configuration of the nodes: Node1 in host1: ``` cluster.name: my_cluster node.name: node1 node.master: true node.data: true node.ingest: true path.data: /mnt/almacenamiento/elasticsearch_data/data2 path.logs: /mnt/almacenamiento/elasticsearch_data/logs bootstrap.memory_lock: true network.host: 0.0.0.0 transport.host: 0.0.0.0 transport.tcp.port: 9300 path.repo: ["/media/backup01"] cluster.initial_master_nodes: ["node1","node2","node3"] discovery.seed_hosts: ["ip-host2:9300","ip-host1:9300","ip-host3:9300"] ``` Node2 in host2: ``` cluster.name: my_cluster node.name: node2 node.master: true node.data: true node.ingest: true path.data: /mnt/discodatos01/elasticsearch_data/data2 path.logs: /mnt/discodatos01/elasticsearch_data/logs bootstrap.memory_lock: true network.host: 0.0.0.0 transport.host: 0.0.0.0 transport.tcp.port: 9300 cluster.initial_master_nodes: ["node1","node2","node3"] path.repo: ["/media/backup01"] discovery.seed_hosts: ["ip-host1:9300","ip-host2:9300","ip-host3:9300"] ``` These first two nodes do start with this configuration and continue to form the cluster in green. Node3 in host3 (new node): ``` cluster.name: my_cluster node.name: node3 node.master: true node.data: true node.ingest: true path.data: /mnt/almacenamiento/elasticsearch_data/data path.logs: /mnt/almacenamiento/elasticsearch_data/logs bootstrap.memory_lock: true network.host: 0.0.0.0 transport.host: 0.0.0.0 transport.tcp.port: 9300 path.repo: ["/media/backup01"] discovery.seed_hosts: ["ip-host2:9300", "ip-host1:9300", "ip-host3:9300"] cluster.initial_master_nodes: ["node1", "node2", "node3"] ``` Next I leave the output of the log of node 3: ``` [2020-06-23T11:22:02,156][INFO][o.e.x.s.a.s.FileRolesStore] [node3] parsed [0] roles from file [/etc/elasticsearch/roles.yml] [2020-06-23T11:22:02,913][INFO][o.e.x.m.p.l.CppLogMessageHandler] [nodee3] [controller/12705] [Main.cc@110] controller (64 bit): Version 7.6.1 (Build 6eb6e036390036) Copyright (c) 2020 Elasticsearch BV [2020-06-23T11:22:03,525][DEBUG][o.e.a.ActionModule] [node3] Using REST wrapper from plugin org.elasticsearch.xpack.security.Security [2020-06-23T11:22:03,692][INFO][o.e.d.DiscoveryModule] [node3] using discovery type [zen] and seed hosts providers [settings] [2020-06-23T11:22:04,592][INFO][o.e.n.Node] [node3] initialized [2020-06-23T11:22:04,592][INFO][o.e.n.Node] [node3] starting ... [2020-06-23T11:22:04,713][INFO][o.e.t.TransportService] [node3] publish_address {ip-host3:9300}, bound_addresses {[::]:9300} [2020-06-23T11:22:05,024][INFO][o.e.b.BootstrapChecks] [node3] bound or publishing to a non-loopback address, enforcing bootstrap checks [2020-06-23T11:22:05,027][ERROR][o.e.b.Bootstrap] [node3] node validation exception [1] bootstrap checks failed [1]: memory locking requested for elasticsearch process but memory is not locked ``` The node has never started and I always get the same "Node validation exception" error message. Where ip-hostX appears, the host IP is actually set. I hope your help. Thank you very much. Regards. ---
**Author:** ![defalt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/defalt/32/71379_2.png) [@defalt](https://discuss.elastic.co/u/defalt)\ **Post date:** [June 23, 2020, 1:15pm UTC](https://discuss.elastic.co/t/i-cant-add-a-new-node-to-my-cluster/238250/2 "2020-06-23T13:15:22Z")
What happens when you start up Node2 and Node 3? Do they connect? What happens when you only start Node3? ---
**Author:** ![dferez](https://avatars.discourse-cdn.com/v4/letter/d/74df32/32.png) [@dferez](https://discuss.elastic.co/u/dferez)\ **Post date:** [June 23, 2020, 2:12pm UTC](https://discuss.elastic.co/t/i-cant-add-a-new-node-to-my-cluster/238250/3 "2020-06-23T14:12:32Z")
Hi. In both cases the same error message "Node validation exception" appears. Thank you. Regards. ---
**Author:** ![defalt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/defalt/32/71379_2.png) [@defalt](https://discuss.elastic.co/u/defalt)\ **Post date:** [June 23, 2020, 2:23pm UTC](https://discuss.elastic.co/t/i-cant-add-a-new-node-to-my-cluster/238250/4 "2020-06-23T14:23:05Z")
> [@dferez](#): > > `memory locking requested for elasticsearch process but memory is not locked` Maybe this is the actual problem. Check this [Elastic Documentation](https://www.elastic.co/guide/en/elasticsearch/reference/7.x/setting-system-settings.html#systemd) ---
**Author:** ![dferez](https://avatars.discourse-cdn.com/v4/letter/d/74df32/32.png) [@dferez](https://discuss.elastic.co/u/dferez)\ **Post date:** [June 23, 2020, 4:07pm UTC](https://discuss.elastic.co/t/i-cant-add-a-new-node-to-my-cluster/238250/5 "2020-06-23T16:07:20Z")
Thank you very much for the help. It works now. Regards. ---
**Author:** ![defalt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/defalt/32/71379_2.png) [@defalt](https://discuss.elastic.co/u/defalt)\ **Post date:** [June 24, 2020, 6:08am UTC](https://discuss.elastic.co/t/i-cant-add-a-new-node-to-my-cluster/238250/6 "2020-06-24T06:08:31Z")
Awesome. Please mark my answer as the solution so that others can find it more easily. 🙂 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 22, 2020, 6:08am UTC](https://discuss.elastic.co/t/i-cant-add-a-new-node-to-my-cluster/238250/7 "2020-07-22T06:08:39Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.