Skip to main content

ElasticSearch - setting [cluster.initial_master_nodes] is not allowed when [discovery.type] is set to [single-node]

Upgrading ElasticSearch can be quite challenging(at least for me it was). I talked about some other issues I had while upgrading before. Let's add a last one to the list...

When talking about the bootstrap check failures in a previous post, I shared my final solution.

But if you were paying attention as a reader you maybe noticed that I didn’t follow the suggestions mentioned inside the bootstrap check error:

bootstrap check failure [1] of [2]: 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

I didn’t set the discovery.seed_hosts, discovery.seed_providers or cluster.initial_master_nodes setting as mentioned, instead I changed the discovery.type to single-node.

In fact my first attempt looked like this:

However this resulted in the following error message:

[2022-05-09T11:33:18,943][WARN ][stderr                   ] [SERVER1] java.lang.IllegalArgumentException: setting [cluster.initial_master_nodes] is not allowed when [discovery.type] is set to [single-node]

[2022-05-09T11:33:18,943][WARN ][stderr                   ] [SERVER1] at org.elasticsearch.cluster.coordination.ClusterBootstrapService.<init>(ClusterBootstrapService.java:87)

[2022-05-09T11:33:18,944][WARN ][stderr                   ] [SERVER1] at org.elasticsearch.cluster.coordination.Coordinator.<init>(Coordinator.java:258)

[2022-05-09T11:33:18,944][WARN ][stderr                   ] [SERVER1] at org.elasticsearch.discovery.DiscoveryModule.<init>(DiscoveryModule.java:191)

[2022-05-09T11:33:18,944][WARN ][stderr                   ] [SERVER1] at org.elasticsearch.node.Node.<init>(Node.java:828)

[2022-05-09T11:33:18,944][WARN ][stderr                   ] [SERVER1] at org.elasticsearch.node.Node.<init>(Node.java:291)

[2022-05-09T11:33:18,944][WARN ][stderr                   ] [SERVER1] at org.elasticsearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:234)

[2022-05-09T11:33:18,944][WARN ][stderr                   ] [SERVER1] at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:234)

[2022-05-09T11:33:18,944][WARN ][stderr                   ] [SERVER1] at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:358)

[2022-05-09T11:33:18,944][WARN ][stderr                   ] [SERVER1] at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:166)

[2022-05-09T11:33:18,945][WARN ][stderr                   ] [SERVER1] at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:157)

[2022-05-09T11:33:18,945][WARN ][stderr                   ] [SERVER1] at org.elasticsearch.common.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:81)

[2022-05-09T11:33:18,945][WARN ][stderr                   ] [SERVER1] at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:112)

[2022-05-09T11:33:18,945][WARN ][stderr                   ] [SERVER1] at org.elasticsearch.cli.Command.main(Command.java:77)

[2022-05-09T11:33:18,945][WARN ][stderr                   ] [SERVER1] at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:122)

[2022-05-09T11:33:18,945][WARN ][stderr                   ] [SERVER1] at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:80)

[2022-05-09T11:33:18,945][WARN ][stderr                   ] [SERVER1] For complete error details, refer to the log at d:\elastic\elasticsearch\logs\elasticsearch.log

By setting the discovery type to single-node, a node will elect itself master and will not join a cluster with any other node.

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more