question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Elasticsearch-OSS] Cannot Start using OSS version

See original GitHub issue

Hi, I am having an error when deploying elasticsearch-oss because is not compatible with node.ml. And the script force to add it. The only way to run it is to edit manually the statefullset and delete:

containers:
      - env:
        - name: node.ml
          value: false,

It doesn’t matter if I set it to false. It crash with this error:

"stacktrace": ["org.elasticsearch.bootstrap.StartupException: java.lang.IllegalArgumentException: unknown setting [node.ml] please check that any required plugins are installed, or check the breaking changes documentation for removed settings",

Chart version: 7.11.1

Kubernetes version: v1.18.9

Kubernetes provider: EKS

Helm Version: v3.5.0

Elasticsearch Version: 7.10.2

Thanks!

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:1
  • Comments:11 (3 by maintainers)

github_iconTop GitHub Comments

3reactions
xrlcommented, Mar 1, 2021

I had the same issue and I read over the templates a bit, looks like they take the entries from the release’s role list and dynamically create ES config properties. The new default values include a ml and remote_cluster_client whose presence, true or false, would put an unsupported config in to my version of ES (7.2.0 which I’m in the process of upgrading, hence this issue).

The fix? Don’t let the helm template see any value for those two bad keys:

# snippet from my logs-master.yaml value file
roles:
  master: "true"
  ingest: "false"
  data: "false"
  ml:
  remote_cluster_client:
1reaction
jmlrtcommented, Mar 3, 2021

Indeed, that’s why we have a different branch for 6.8 which doesn’t include ml and remote_cluster_client in default values + tags for every releases and we specify here that you should use an Helm chart version is aligned to the version of the product you want to deploy.

We recommend that the Helm chart version is aligned to the version of the product you want to deploy. This will ensure that you using a chart version that has been tested against the corresponding production version. This will also ensure that the documentation and examples for the chart will work with the version of the product you are installing.

For example if you want to deploy an Elasticsearch 7.7.1 cluster, use the corresponding 7.7.1 tag.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Elasticsearch version 6.8.6 oss unable to start - Elastic Discuss
Hi all,. I am trying to do a fresh install of elasticsearch-oss-6.8.6 with OpenJDK version 1.8.0_181. An elasticsearch-oss-6.5 was able to ...
Read more >
Troubleshoot - Open Distro Documentation
If you run sudo yum upgrade and receive a dependency error, Elasticsearch OSS likely has a new minor version that the Open Distro...
Read more >
Upgrade from Elasticsearch OSS to OpenSearch
If your existing cluster runs an older version of Elasticsearch OSS, the first step is to upgrade to version 6.x or 7.x. Elasticsearch...
Read more >
OpenSearch: The Open Source Successor of Elasticsearch?
Update: On 12 July 2021, OpenSearch reached general availability with the release of v1.0. You can find more information on the GA release...
Read more >
What is Amazon OpenSearch Service? - AWS Documentation
OpenSearch is a fully open-source search and analytics engine for use ... OpenSearch Service also supports the following legacy Elasticsearch OSS versions:.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found