# Trouble getting an new node added to a cluster

**URL:** <https://discuss.elastic.co/t/trouble-getting-an-new-node-added-to-a-cluster/234814>\
**Category:** Elasticsearch\
**Created:** [May 28, 2020, 8:11pm UTC](https://discuss.elastic.co/t/trouble-getting-an-new-node-added-to-a-cluster/234814 "2020-05-28T20:11:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andreas\_Falk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andreas_falk/32/82595_2.png) [@Andreas\_Falk](https://discuss.elastic.co/u/Andreas_Falk)\
**Post date:** [May 28, 2020, 8:11pm UTC](https://discuss.elastic.co/t/trouble-getting-an-new-node-added-to-a-cluster/234814/1 "2020-05-28T20:11:07Z")

</div>

Hi,

When trying to add the new node to the cluster it fails on bootstrapcheck.

```auto
[2020-05-28T20:05:45,054][INFO][o.e.t.TransportService] [log04] publish_address {192.168.2.194:9300}, bound_addresses {192.168.2.194:9300}
[2020-05-28T20:05:45,426][INFO][o.e.b.BootstrapChecks] [log04] bound or publishing to a non-loopback address, enforcing bootstrap checks
[2020-05-28T20:05:45,436][ERROR][o.e.b.Bootstrap] [log04] node validation exception
[1] bootstrap checks failed
[1]: JVM is using the serial collector but should not be for the best performance; either it's the default for the VM [OpenJDK 64-Bit Server VM] or -XX:+UseSerialGC was explicitly specified

```

It is an ubuntu 20.04, with the default embedded OpenJDK.

Do you guys know of any "bugs" on Ubuntu 20.04 and Elasticserch 7.7.0?

--  
Regards Falk

---

<div class="post-metadata">

**Author:** ![dev\_dull](https://avatars.discourse-cdn.com/v4/letter/d/f0a364/32.png) [@dev\_dull](https://discuss.elastic.co/u/dev_dull)\
**Post date:** [June 4, 2020, 11:30pm UTC](https://discuss.elastic.co/t/trouble-getting-an-new-node-added-to-a-cluster/234814/2 "2020-06-04T23:30:02Z")

</div>

I ran into the same thing. Took me a while digging through the chain of shell scripts to figure out a fix. Hopefully this'll save someone else some headache.

I had to modify the systemd unit file with a new environment variable to force java off of the "Serial Garbage Collector"

Note that paths may vary depending on OS (I'm on CentOS):

```auto
root@linux# cd /lib/systemd/system

```

Modify `elasticsearch.service`  
In the `[Service]` section, add the following with the other `Environment=` lines

```auto
Environment=ES_JAVA_OPTS=-XX:+UseParallelGC

```

save and exit the file.  
run

```auto
root@linux# systemctl daemon-reload

```

The elasticsearch service should now start up.

---

<div class="post-metadata">

**Author:** ![Andreas\_Falk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andreas_falk/32/82595_2.png) [@Andreas\_Falk](https://discuss.elastic.co/u/Andreas_Falk)\
**Post date:** [June 8, 2020, 7:16pm UTC](https://discuss.elastic.co/t/trouble-getting-an-new-node-added-to-a-cluster/234814/3 "2020-06-08T19:16:00Z")

</div>

Thanks for the answer.

For me it ended with using our 20.04 as docker hosts 🙂  
And it works for the cold nodes atleast 🙂

---

<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 6, 2020, 7:16pm UTC](https://discuss.elastic.co/t/trouble-getting-an-new-node-added-to-a-cluster/234814/4 "2020-07-06T19:16:01Z")

</div>

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