Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ElasticSearch unknown settings [cluster.initial_master_nodes] #2531

Closed
jeremynikolic opened this issue Mar 11, 2020 · 3 comments
Closed

ElasticSearch unknown settings [cluster.initial_master_nodes] #2531

jeremynikolic opened this issue Mar 11, 2020 · 3 comments

Comments

@jeremynikolic
Copy link

Description:

I encountered a bug when using older version of ElasticSearch. I thought it would be nice to document it somewhere and help others save a bit of time finding the issue.

The docker-compose contains a line that can prevent ElasticSearch older versions (<7 I believe) to crash on startup:
- cluster.initial_master_nodes=laradock-node

If present for old version, this will result in the following error
unknown settings [cluster.initial_master_nodes] ...

Solution

Remove the line in docker-compose.yml
I don't know if this could be a conditional environment value

@jeremynikolic jeremynikolic changed the title unknown settings [cluster.initial_master_nodes] ElasticSearch unknown settings [cluster.initial_master_nodes] Mar 11, 2020
@hainovsky
Copy link

hainovsky commented May 1, 2020

Looks like both lines which were added in this commit should be commented out for older version:
- node.name=laradock-node
- cluster.initial_master_nodes=laradock-node

For me, it also required removing old ES volume: docker volume rm laradock_elasticsearch

@stale
Copy link

stale bot commented Jul 30, 2020

Hi 👋 this issue has been automatically marked as stale 📌 because it has not had recent activity 😴. It will be closed if no further activity occurs. Thank you for your contributions ❤️.

@stale stale bot added the Stale label Jul 30, 2020
@stale
Copy link

stale bot commented Aug 21, 2020

Hi again 👋 we would like to inform you that this issue has been automatically closed 🔒 because it had not recent activity during the stale period. We really really appreciate your contributions, and looking forward for more in the future 🎈.

@stale stale bot closed this as completed Aug 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants