Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Node and elasticSearch client - The client noticed that the server is not a supported distribution of Elasticsearch

I'm using @elastic/elasticsearch version ^7.5.0 and Node 14. Everything worked fine, until I ran yarn upgrade which made various changes in my yarn.lock file and since then I'm getting the following error:

The client noticed that the server is not a supported distribution of Elasticsearch

I tried upgrading @elastic/elasticsearch to latest version ^7.14.0, but this did not resolve the issue.

Nothing changed in AWS configuration either, what can be the cause for this error?

Please advise.

like image 468
David Faizulaev Avatar asked Aug 23 '21 11:08

David Faizulaev


People also ask

Is the server a supported distribution of Elasticsearch?

The client noticed that the server is not a supported distribution of Elasticsearch. · Issue #1429 · elastic/elasticsearch-ruby · GitHub Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Is Elasticsearch free to use with AWS?

@anderslemke you can use the default distribution of Elasticsearch, which is free to use under Elastic License v2. Sorry, something went wrong. is there any fix for this? I'm using the latest version available on aws 7.10, also using latest ruby gem version and still getting this error. Sorry, something went wrong. Still waiting for fix as well..

What version of Elasticsearch do I need to upgrade to?

With the 7.11 release of Elasticsearch, we will no longer be releasing oss-only distributions, as stated in the FAQ on license change. The recommendation is to upgrade to the latest default distribution of Elasticsearch, which is free to use under Elastic License v2. Otherwise, you can pin the client version to <7.14. Sorry, something went wrong.


Video Answer


2 Answers

Resolved by upgrading to @elastic/elasticsearch 7.13.0

https://github.com/elastic/elasticsearch-js/issues/1519

like image 178
David Faizulaev Avatar answered Oct 17 '22 11:10

David Faizulaev


Basically, all Elastic clients are going to be updated to not work with anything else than official Elastic versions: https://www.theregister.com/2021/08/09/elasticsearch_python_client_change/

That somehow makes sense since AWS ES (soon Opensearch) and Elasticsearch (by Elastic) are going to be completely different products, so it would make no sense to have one client to rule them all.

When taking the decision to fork the underlying engine (i.e. the elasticsearch project), one also has to fork the related clients since those clients are mainly working through APIs that will diverge anyway.

like image 36
Val Avatar answered Oct 17 '22 09:10

Val