Operate 8.0.1 not supporting Elasticsearch 8.1.3?

We are about to migrate our ELK to 8.1.3 and I was checking if the latest Zeebe and Operate versions do deal with it properly.

Zeebe started fine and the exporter did create the indexes as usual.

Operate did also start, created the below indexes

  • operate-batch-operation-1.0.0_
  • operate-decision-instance-1.0.0_
  • operate-event-1.0.0_
  • operate-flownode-instance-1.3.0_
  • operate-incident-1.3.0_
  • operate-list-view-1.3.0_
  • operate-operation-1.0.0_
  • operate-sequence-flow-1.0.0_
  • operate-variable-1.1.0_

but then the log shows lots of errors and the data from Zeebe is not imported. The referred index was not created.

Any idea?

2022-04-29 10:52:33.142 INFO 10 — [ main] i.c.o.s.SchemaStartup : SchemaStartup started.
2022-04-29 10:52:33.142 INFO 10 — [ main] i.c.o.s.SchemaStartup : SchemaStartup: validate schema.
2022-04-29 10:52:33.536 INFO 10 — [ main] i.c.o.s.SchemaStartup : SchemaStartup: schema is empty or not complete. Indices will be created.
2022-04-29 10:52:33.538 INFO 10 — [ main] i.c.o.s.ElasticsearchSchemaManager : Create default settings from ‘operate_template’ with 1 shards and 1 replicas per index.
2022-04-29 10:52:33.743 WARN 10 — [ main] i.c.o.u.RetryOperation : Elasticsearch exception [type=illegal_argument_exception, reason=Unknown token [VALUE_NULL] in alias [operate-migration-steps-repository-1.1.0_alias]]
2022-04-29 10:52:35.751 WARN 10 — [ main] i.c.o.u.RetryOperation : Elasticsearch exception [type=illegal_argument_exception, reason=Unknown token [VALUE_NULL] in alias [operate-migration-steps-repository-1.1.0_alias]]
2022-04-29 10:52:37.758 WARN 10 — [ main] i.c.o.u.RetryOperation : Elasticsearch exception [type=illegal_argument_exception, reason=Unknown token [VALUE_NULL] in alias [operate-migration-steps-repository-1.1.0_alias]]
2022-04-29 10:52:39.764 WARN 10 — [ main] i.c.o.u.RetryOperation : Elasticsearch exception [type=illegal_argument_exception, reason=Unknown token [VALUE_NULL] in alias [operate-migration-steps-repository-1.1.0_alias]]
2022-04-29 10:52:41.772 WARN 10 — [ main] i.c.o.u.RetryOperation : Elasticsearch exception [type=illegal_argument_exception, reason=Unknown token [VALUE_NULL] in alias [operate-migration-steps-repository-1.1.0_alias]]
2022-04-29 10:52:43.778 WARN 10 — [ main] i.c.o.u.RetryOperation : Elasticsearch exception [type=illegal_argument_exception, reason=Unknown token [VALUE_NULL] in alias [operate-migration-steps-repository-1.1.0_alias]]
2022-04-29 10:52:45.784 WARN 10 — [ main] i.c.o.u.RetryOperation : Elasticsearch exception [type=illegal_argument_exception, reason=Unknown token [VALUE_NULL] in alias [operate-migration-steps-repository-1.1.0_alias]]
2022-04-29 10:52:47.793 WARN 10 — [ main] i.c.o.u.RetryOperation : Elasticsearch exception [type=illegal_argument_exception, reason=Unknown token [VALUE_NULL] in alias [operate-migration-steps-repository-1.1.0_alias]]
2022-04-29 10:52:49.800 WARN 10 — [ main] i.c.o.u.RetryOperation : Elasticsearch exception [type=illegal_argument_exception, reason=Unknown token [VALUE_NULL] in alias [operate-migration-steps-repository-1.1.0_alias]]
2022-04-29 10:52:51.807 WARN 10 — [ main] i.c.o.u.RetryOperation : Elasticsearch exception [type=illegal_argument_exception, reason=Unknown token [VALUE_NULL] in alias [operate-migration-steps-repository-1.1.0_alias]]
2022-04-29 10:52:53.817 WARN 10 — [ main] i.c.o.u.RetryOperation : Elasticsearch exception [type=illegal_argument_exception, reason=Unknown token [VALUE_NULL] in alias [operate-migration-steps-repository-1.1.0_alias]]
2022-04-29 10:52:55.826 WARN 10 — [ main] i.c.o.u.RetryOperation : Elasticsearch exception [type=illegal_argument_exception, reason=Unknown token [VALUE_NULL] in alias [operate-migration-steps-repository-1.1.0_alias]]
2022-04-29 10:52:57.833 WARN 10 — [ main] i.c.o.u.RetryOperation : Elasticsearch exception [type=illegal_argument_exception, reason=Unknown token [VALUE_NULL] in alias [operate-migration-steps-repository-1.1.0_alias]]
2022-04-29 10:52:59.841 WARN 10 — [ main] i.c.o.u.RetryOperation : Elasticsearch exception [type=illegal_argument_exception, reason=Unknown token [VALUE_NULL] in alias [operate-migration-steps-repository-1.1.0_alias]]
2022-04-29 10:53:01.848 WARN 10 — [ main] i.c.o.u.RetryOperation : Elasticsearch exception [type=illegal_argument_exception, reason=Unknown token [VALUE_NULL] in alias [operate-migration-steps-repository-1.1.0_alias]]
2022-04-29 10:53:03.854 WARN 10 — [ main] i.c.o.u.RetryOperation : Elasticsearch exception [type=illegal_argument_exception, reason=Unknown token [VALUE_NULL] in alias [operate-migration-steps-repository-1.1.0_alias]]
2022-04-29 10:53:05.860 WARN 10 — [ main] i.c.o.u.RetryOperation : Elasticsearch exception [type=illegal_argument_exception, reason=Unknown token [VALUE_NULL] in alias [operate-migration-steps-repository-1.1.0_alias]]
2022-04-29 10:53:07.876 WARN 10 — [ main] i.c.o.u.RetryOperation : Elasticsearch exception [type=illegal_argument_exception, reason=Unknown token [VALUE_NULL] in alias [operate-migration-steps-repository-1.1.0_alias]]
2022-04-29 10:53:09.887 WARN 10 — [ main] i.c.o.u.RetryOperation : Elasticsearch exception [type=illegal_argument_exception, reason=Unknown token [VALUE_NULL] in alias [operate-migration-steps-repository-1.1.0_alias]]
2022-04-29 10:53:11.895 WARN 10 — [ main] i.c.o.u.RetryOperation : Elasticsearch exception [type=illegal_argument_exception, reason=Unknown token [VALUE_NULL] in alias [operate-migration-steps-repository-1.1.0_alias]]
2022-04-29 10:53:11.895 INFO 10 — [ main] i.c.o.u.RetryOperation : CreateIndex operate-migration-steps-repository-1.1.0_ - Waiting 2 SECONDS. 20/300

Defining the index aliases with {“is_write_index”:null} seems not to work with ES 8.1.
Created those indexes manually, but then Operate complained during creation of documents in brixdev-operate-migration-steps-repository-1.1.0_ that it is “unable to parse response body”. It retried many times, the POD was even killed by K8s couple of times, then it “gave up” and Operate started.
Please check what you can do to make Operate work w/o manual interactions with Elastic 8.1

Hello!

Did you found out the problem? I faced with the same problem

Hi @Dias_Alpysbayev, unfortunately not, I’m still waiting for this.

Afaik Camunda Platform doesn’t support Elastic 8.x

Greets
Chris

Oh… So, I cannot launch it by docker? Do you know any alternatives except cloud?

You can use Elastic 7.x this should work. Did you tried that ?

Indeed it works with Elastic 7.x. But since we want to upgrade our ES cluster to 8.x this incompatibility blocks us from doing so.

Maybe @felix-mueller can share some information about plans when we will support elastic 8.x :slight_smile: