Open ChrisKujawa opened 4 weeks ago
There's an issue deserializing index template 95, saying there is no type field.
Elasticsearch 7.x does not need a type field but as per the 8.15
documentation here a type
field is needed for a lowercase normalizer.
Given we use the 8.x version of the elasticsearch-java
client when deserializing it expects the type field.
In operate-list-view.json
I updated this field to have the type
I think the issue is this.
operate-list-view
Possible fixes: Depending on how quick this is needed to be alleviated
@EuroLew couldn't the conflict come from the Operate Importer?
If we are starting fresh with an empty elasticsearch this issue shouldn't occur as we would create the template correctly. This only occurs if an old version of the template exists I assumed it was the case since some of these errored namespaces are over a month old that a. we had a camunda instance, we turned on the exporter (This would error as the importer created the indices and theres a conflict) Or b. If we start from fresh with importer and exporter then yes there is a race condition that could cause this if the importer gets to create the index first
We likely should resolve this via https://github.com/camunda/camunda/issues/22897
@sdorokhova could we already fix this https://github.com/camunda/camunda/issues/22897 so we resolve this issue here?
Description
Reported on INT with our RC for alpha1
https://console.cloud.google.com/errors/detail/CI7_od-oyLDzSA;service=zeebe;time=P7D;locations=global?project=camunda-saas-int