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 another one to the list...
One of the ways how ElasticSearch helps you to do the right things is to do some bootstrap checks. These bootstrap checks inspect a variety of Elasticsearch and system settings and compare them to values that are safe for the operation of Elasticsearch. If Elasticsearch is in development mode, any bootstrap checks that fail appear as warnings in the Elasticsearch log. If Elasticsearch is in production mode, any bootstrap checks that fail will cause Elasticsearch to refuse to start.
In this case the bootstrap checks returned the following errors:
[2022-05-09T09:53:42,647][ERROR][o.e.b.Bootstrap ] [SERVER1] node validation exception
[2] bootstrap checks failed. You must address the points described in the following [2] lines before starting Elasticsearch.
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
bootstrap check failure [2] of [2]: Transport SSL must be enabled if security is enabled. Please set [xpack.security.transport.ssl.enabled] to [true] or disable security by setting [xpack.security.enabled] to [false]
[2022-05-09T09:53:42,651][INFO ][o.e.n.Node ] [SERVER1] stopping ...
[2022-05-09T09:53:42,723][INFO ][o.e.n.Node ] [SERVER1] stopped
[2022-05-09T09:53:42,724][INFO ][o.e.n.Node ] [SERVER1] closing ...
[2022-05-09T09:53:42,736][INFO ][o.e.n.Node ] [SERVER1] closed
This was a local development cluster with only one node where I didn’t want to add security. So I fixed the bootstrap check errors by updating my elasticsearch.yml
to the following: