Getting fatal exception while booting Elasticsearch while trying to start elasticsearch in Vm

Elastic Stack Elasticsearch
1

getting this error

fatal exception while booting Elasticsearch

java.lang.IllegalStateException: cannot downgrade a node from version [8.10.3] to version [8.9.0]
	at org.elasticsearch.env.NodeMetadata.verifyUpgradeToCurrentVersion(NodeMetadata.java:129) ~[elasticsearch-8.9.0.jar:?]
	at org.elasticsearch.env.NodeMetadata.upgradeToCurrentVersion(NodeMetadata.java:136) ~[elasticsearch-8.9.0.jar:?]
	at org.elasticsearch.env.NodeEnvironment.loadNodeMetadata(NodeEnvironment.java:634) ~[elasticsearch-8.9.0.jar:?]
	at org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:333) ~[elasticsearch-8.9.0.jar:?]
	at org.elasticsearch.node.Node.<init>(Node.java:490) ~[elasticsearch-8.9.0.jar:?]
	at org.elasticsearch.node.Node.<init>(Node.java:334) ~[elasticsearch-8.9.0.jar:?]
	at org.elasticsearch.bootstrap.Elasticsearch$2.<init>(Elasticsearch.java:234) ~[elasticsearch-8.9.0.jar:?]
	at org.elasticsearch.bootstrap.Elasticsearch.initPhase3(Elasticsearch.java:234) ~[elasticsearch-8.9.0.jar:?]
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:72) ~[elasticsearch-8.9.0.jar:?]

but all the nodes have 8.9.0 version

2 
cluster.name: es-hotel-meta-indexer
node.name: "es-hotel-meta-master-1"
path.logs: /var/log/elasticsearch
path.data: /data
network.host: 0.0.0.0
discovery.seed_hosts: ["http://es-hotel-meta-indexer-1.com","http://es-hotel-meta-indexer-2.com","http://es-hotel-meta-indexer-3.com"]
cluster.initial_master_nodes: ["http://es-hotel-meta-indexer-1.com","http://es-hotel-meta-indexer-2.com","http://es-hotel-meta-indexer-3.com"]
http.port: 9200
xpack.security.enabled: false

all other nodes have similar config just the node name changes

3

This error isn't related to the current version of the Elasticsearch instances you're trying to start, but implies that you'd previously started an Elasticsearch instance that was using version 8.10.3 that wrote data to the same place one of these instances is trying to read from.

This is controlled by this config:

path.data: /data

If you don't care about whatever was saved in there by an 8.10.3 instance, you can do rm -rf /data/*. If you do care about that old data, just create a new dir like /data-8.9.0 and change all the configs for these new instances to point to the new path.

4

thanks for the reply

tried upgrading the elasticsearch and it is working fine now

1 Like
5

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