You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 16, 2023. It is now read-only.
Describe the bug:
Using elastisearch 7.15.0 [imageTag: "7.15.0"] , you cannot create frozen data_frozen dedicated node, adding "data_frozen: "true" yeilds in the below error on elasticsearch pod:
{"type": "deprecation.elasticsearch", "timestamp": "2021-10-24T11:42:12,686Z", "level": "DEPRECATION", "component": "o.e.d.n.Node", "cluster.name": "qa-elasticsearch", "node.name": "qa-elasticsearch-frozen-0", "message": "legacy role settings [node.data_frozen, node.data, node.remote_cluster_client, node.ingest, node.master, node.ml] are deprecated, use [node.roles=[data_frozen]]", "key": "legacy role settings" }
{"type": "server", "timestamp": "2021-10-24T11:42:15,321Z", "level": "ERROR", "component": "o.e.b.ElasticsearchUncaughtExceptionHandler", "cluster.name": "qa-elasticsearch", "node.name": "qa-elasticsearch-frozen-0", "message": "uncaught exception in thread [main]",
"stacktrace": ["org.elasticsearch.bootstrap.StartupException: java.lang.IllegalArgumentException: unknown setting [node.data_frozen] please check that any required plugins are installed, or check the breaking changes documentation for removed settings",
"at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:171) ~[elasticsearch-7.15.0.jar:7.15.0]",
"at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:158) ~[elasticsearch-7.15.0.jar:7.15.0]",
"at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:75) ~[elasticsearch-7.15.0.jar:7.15.0]",
"at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:114) ~[elasticsearch-cli-7.15.0.jar:7.15.0]",
"at org.elasticsearch.cli.Command.main(Command.java:79) ~[elasticsearch-cli-7.15.0.jar:7.15.0]",
"at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:123) ~[elasticsearch-7.15.0.jar:7.15.0]",
"at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:81) ~[elasticsearch-7.15.0.jar:7.15.0]",
"Caused by: java.lang.IllegalArgumentException: unknown setting [node.data_frozen] please check that any required plugins are installed, or check the breaking changes documentation for removed settings",
"at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:533) ~[elasticsearch-7.15.0.jar:7.15.0]",
"at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:478) ~[elasticsearch-7.15.0.jar:7.15.0]",
"at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:449) ~[elasticsearch-7.15.0.jar:7.15.0]",
"at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:420) ~[elasticsearch-7.15.0.jar:7.15.0]",
"at org.elasticsearch.common.settings.SettingsModule.<init>(SettingsModule.java:138) ~[elasticsearch-7.15.0.jar:7.15.0]",
"at org.elasticsearch.node.Node.<init>(Node.java:452) ~[elasticsearch-7.15.0.jar:7.15.0]",
"at org.elasticsearch.node.Node.<init>(Node.java:288) ~[elasticsearch-7.15.0.jar:7.15.0]",
"at org.elasticsearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:219) ~[elasticsearch-7.15.0.jar:7.15.0]",
"at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:219) ~[elasticsearch-7.15.0.jar:7.15.0]",
"at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:399) ~[elasticsearch-7.15.0.jar:7.15.0]",
"at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:167) ~[elasticsearch-7.15.0.jar:7.15.0]",
"... 6 more"] }
uncaught exception in thread [main]
java.lang.IllegalArgumentException: unknown setting [node.data_frozen] please check that any required plugins are installed, or check the breaking changes documentation for removed settings
at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:533)
at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:478)
at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:449)
at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:420)
at org.elasticsearch.common.settings.SettingsModule.<init>(SettingsModule.java:138)
at org.elasticsearch.node.Node.<init>(Node.java:452)
at org.elasticsearch.node.Node.<init>(Node.java:288)
at org.elasticsearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:219)
at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:219)
at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:399)
at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:167)
at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:158)
at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:75)
at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:114)
at org.elasticsearch.cli.Command.main(Command.java:79)
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:123)
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:81)
For complete error details, refer to the log at /usr/share/elasticsearch/logs/qa-elasticsearch.log
Trying to use node.roles: [ data_frozen ] yields another error of : can not explicitly configure node roles and use legacy role setting as the chart seems to explicitly use the legacy settings for node roles using the environment variables, I can see roles have changed and it looks it support data_cold ( but still cannot see data_frozen) but this is available on version 8.0.0 of image tag which I won't use as my cluster is 7.15.0
Steps to reproduce:
Deploy elasticsearch 7.15.0 cluster using helm chart.
Try to deploy "Frozen Data Tier dedicated nodes" using either the roles tag in the values.yamlor node.roles: [ data_frozen ] settings, both will fail
Expected behavior:
Able to deploy and create data_frozen nodes using the 7.15.0 helm chart, looks doable in the 8.0.0-Snapshot ( not tested though!)
The text was updated successfully, but these errors were encountered:
In this case, Elasticsearch node crashes with the following FATAL error:
"Caused by: java.lang.IllegalArgumentException: unknown setting
[node.data_frozen] please check that any required plugins are installed, or
check the breaking changes documentation for removed settings",
Trying to set it in elasticsearch.yml. also doesn't work:
In this case, Elasticsearch node crashes with the following:
"at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:167)
~[elasticsearch-7.15.1.jar:7.15.1]",
"... 6 more"] }
uncaught exception in thread [main]
java.lang.IllegalArgumentException: can not explicitly configure node roles
and use legacy role setting [node.data]=[true]
"Suppressed: java.lang.IllegalArgumentException: unknown setting [node.data_hot] please check that any required plugins are installed, or check the breaking changes documentation for removed settings"
Hi, data_frozen and data_hot roles aren't supported yet with this chart.
The only roles supported are: master, ingest, data, ml and remote_cluster_client.
The other roles will be supported with 8.0.0 as this required a refactoring which is a breaking change.
If you really need to use some other roles, you can still fork the chart and add backport #1186 on your fork.
Chart version:
7.15.0
Kubernetes version:
1.21
Kubernetes provider: E.g. GKE (Google Kubernetes Engine)
AWS EKS
Helm Version:
3.6.3
helm get release
outputOutput of helm get release
Describe the bug:
Using elastisearch 7.15.0 [
imageTag: "7.15.0"
] , you cannot create frozendata_frozen
dedicated node, adding"data_frozen: "true"
yeilds in the below error on elasticsearch pod:Trying to use node.roles: [ data_frozen ] yields another error of :
can not explicitly configure node roles and use legacy role setting
as the chart seems to explicitly use the legacy settings for node roles using the environment variables, I can see roles have changed and it looks it support data_cold ( but still cannot see data_frozen) but this is available on version8.0.0
of image tag which I won't use as my cluster is7.15.0
Steps to reproduce:
values.yaml
ornode.roles: [ data_frozen ]
settings, both will failExpected behavior:
Able to deploy and create data_frozen nodes using the 7.15.0 helm chart, looks doable in the 8.0.0-Snapshot ( not tested though!)
The text was updated successfully, but these errors were encountered: