Applying Index setting index.routing.allocation.require._name blocks Optimize start up

[venetrius]

Environment (Required on creation)

3.14

Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket)

After applying index.routing.allocation.require._name index settings, Optimize fail to start.

Steps to reproduce (Required on creation)

1. Run an instance of Camunda run 7.22.
2. Run an instance of Optimize 3.14 demo (with included Elasticsearch)
3. Wait for Optimize to boot successfully and ensure it is running and you can see the data
4. Run the following curl command to view the default index settings:

curl "localhost:9200/optimize-decision-instance-invoice-assign-approver_v5/_settings?pretty"

5. Run the following curl command to add index.routing.allocation.require:

curl -X PUT "localhost:9200/optimize-decision-instance-invoice-assign-approver_v5/_settings?pretty" -H 'Content-Type: application/json' -d'
{
  "index.routing.allocation.require._name": "null"
}

6. Repeat 4 to check the config has applied
7. Restart Optimize and it will fail with the error seen in the clients' description

Observed Behavior (Required on creation)

On start up Optimize BE produces error:

16:32:5021:32:50.284 - Error deserializing co.elastic.clients.elasticsearch.indices.IndexRoutingAllocation: Unknown field 'require' (JSON path: ['optimize-dev-simulation-process-instance-projetgatlingsim3_v8'].settings.index.routing.allocation.require) (line no=1, column no=3924, offset=3923)

Expected behavior (Required on creation)

Root Cause (Required on prioritization)

This is caused by ES client class IndexRoutingAllocation not having the require field in combination with withJson method using the INSTANCE_REJECT_UNKNOWN_FIELDS setting

Solution Ideas

Hints

Links

• Support case: https://jira.camunda.com/browse/SUPPORT-24421
• This bug is fixed by: https://github.com/camunda/camunda-optimize/pull/14640

Breakdown

Pull Requests

Beta Give feedback

1. https://github.com/camunda/camunda-optimize/pull/14640
2. https://github.com/camunda/camunda-optimize/pull/14690

Dev2QA handover

• Does this ticket need a QA test and the testing goals are not clear from the description? Add a Dev2QA handover comment

[KarpovIvan]

Camunda 7 PR: https://github.com/camunda/camunda-optimize/pull/14640
Camunda 8 PR: camunda/camunda#24632

[RomanJRW]

C8 handled in camunda/camunda#24642

[tasso94]

Hi @KarpovIvan, the customer needs a fix for 3.14 as well. Can you please backport this?

[KarpovIvan]

Hi @tasso94, sure np

[KarpovIvan]

https://github.com/camunda/camunda-optimize/pull/14690 - 3.14