# Problems when upgrading from 7.5.2 to 7.6.0 **URL:** \ **Category:** Elasticsearch\ **Created:** [February 12, 2020, 11:23am UTC](https://discuss.elastic.co/t/problems-when-upgrading-from-7-5-2-to-7-6-0/218960 "2020-02-12T11:23:46Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Jan-Philipp\_Bolle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jan-philipp_bolle/32/62534_2.png) [@Jan-Philipp\_Bolle](https://discuss.elastic.co/u/Jan-Philipp_Bolle)\ **Post date:** [February 12, 2020, 11:23am UTC](https://discuss.elastic.co/t/problems-when-upgrading-from-7-5-2-to-7-6-0/218960/1 "2020-02-12T11:23:46Z")
Hi, i using elasicsearch in a docker container with 3 nodes. The configuration I have been using for a long time looks like this: - node.name=pear10 - discovery.seed\_hosts=xxx.xx.xx.230,xxx.xx.xx.231,xxx.xx.xx.232 - cluster.initial\_master\_nodes=xxx.xx.xx.230,xxx.xx.xx.231,xxx.xx.xx.232 - cluster.name=monitoring-cluster - bootstrap.memory\_lock=true After the upgrade to 7.6.0 i got the following error: ERROR: setting [cluster.initial\_master\_nodes] already set, saw [xxx.xx.xx.230,xxx.xx.xx.231,xxx.xx.xx.232] and [xxx.xx.xx.230,xxx.xx.xx.231,xxx.xx.xx.232] If i remove the settings i got a new error: the default discovery settings are unsuitable for production use; at least one of [discovery.seed\_hosts, discovery.seed\_providers, cluster.initial\_master\_nodes] must be configured any idea that might help me regards Philipp ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [February 12, 2020, 11:25am UTC](https://discuss.elastic.co/t/problems-when-upgrading-from-7-5-2-to-7-6-0/218960/2 "2020-02-12T11:25:31Z")
By "remove the settings" do you mean you removed just `cluster.initial_master_nodes` or did you also remove `discovery.seed_hosts`? You should leave `discovery.seed_hosts` in place. ---
**Author:** ![Jan-Philipp\_Bolle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jan-philipp_bolle/32/62534_2.png) [@Jan-Philipp\_Bolle](https://discuss.elastic.co/u/Jan-Philipp_Bolle)\ **Post date:** [February 12, 2020, 11:31am UTC](https://discuss.elastic.co/t/problems-when-upgrading-from-7-5-2-to-7-6-0/218960/3 "2020-02-12T11:31:45Z")
thank you very much for your quick response. i have removed step by step every setting. only the error message changed slightly until there was no more setting. Then i got: the default discovery settings are unsuitable for production use; at least one of [discovery.seed\_hosts, discovery.seed\_providers, cluster.initial\_master\_nodes] must be configured For Example with discovery.seed\_host i got: ERROR: setting [discovery.seed\_hosts] already set, saw [xxx.xx.xx.230,xxx.xx.xx.231,xxx.xx.xx.232] and [xxx.xx.xx.230,xxx.xx.xx.231,xxx.xx.xx.232] ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [February 12, 2020, 12:07pm UTC](https://discuss.elastic.co/t/problems-when-upgrading-from-7-5-2-to-7-6-0/218960/4 "2020-02-12T12:07:23Z")
Ok, thanks, that clarifies the situation. It seems that Elasticsearch is picking up these settings twice for some reason. Can you describe your setup a bit more precisely? Are you [using `docker-compose` like in the manual](https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html)? If so, can you share the full `docker-compose.yml`? If not, how are you orchestrating these nodes? (I tried running `docker-compose` as documented and did not see the effect you are describing) ---
**Author:** ![Jan-Philipp\_Bolle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jan-philipp_bolle/32/62534_2.png) [@Jan-Philipp\_Bolle](https://discuss.elastic.co/u/Jan-Philipp_Bolle)\ **Post date:** [February 12, 2020, 2:16pm UTC](https://discuss.elastic.co/t/problems-when-upgrading-from-7-5-2-to-7-6-0/218960/5 "2020-02-12T14:16:20Z")
thanks a lot it works now. The problem was that we build our own container. That's so we could put the uid in (we work with a uid other than 1000). After I took all changes from [https://github.com/elastic/dockerfiles/tree/v7.6.0/elasticsearch](https://github.com/elastic/dockerfiles/tree/v7.6.0/elasticsearch) it worked. Of course it would be nice to use the original buildscript. Some projects such as grafana allow you to parameterize the build like : docker build --build-arg GF\_UID=714 --build-arg GF\_GID=714 regards Philipp ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 11, 2020, 2:16pm UTC](https://discuss.elastic.co/t/problems-when-upgrading-from-7-5-2-to-7-6-0/218960/6 "2020-03-11T14:16:31Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.