Operate deprecation message when using Elastic 7.16

Camunda 8 Topics Discussion & Questions
1

Hi

Operate logs are getting spammed with deprecation messages after we upgraded to ELK 7.16.1.

WARN 8 — [ Thread-0] o.e.c.RestClient : request [POST https:///operate-operation-1.0.0_/_search?typed_keys=true&max_concurrent_shard_requests=5&ignore_unavailable=true&expand_wildcards=open&allow_no_indices=true&ignore_throttled=false&search_type=query_then_fetch&batched_reduce_size=512] returned 1 warnings: [299 Elasticsearch-7.16.1-5b38441b16b1ebb16a27c107a4c3865776e20c53 “[ignore_throttled] parameter is deprecated because frozen indices have been deprecated. Consider cold or frozen tiers in place of frozen indices.”]

Any option I can set to suppress them (so ignore_throttled=false is not used in the queries)?

Thanks, Fritzi

2

Same with 7.16.3. Wondering if nobody faces this except me. My cluster log is getting spammed with these warnings. Would be really nice to have a setting to change this flag for operate.

2022-02-24 07:43:18.454 WARN 8 — [ postimport_1] o.e.c.RestClient : request [POST https://<elastic.url>/brixdev-operate-flownode-instance-1.3.0_alias/_search?typed_keys=true&max_concurrent_shard_requests=5&ignore_unavailable=true&expand_wildcards=open&allow_no_indices=true&ignore_throttled=false&scroll=60000ms&search_type=query_then_fetch&batched_reduce_size=512] returned 1 warnings: [299 Elasticsearch-7.16.3-4e6e4eab2297e949ec994e688dad46290d018022 “[ignore_throttled] parameter is deprecated because frozen indices have been deprecated. Consider cold or frozen tiers in place of frozen indices.”]

3

Hello @fvogl ,

This is related to Disable specific deprecation warnings - Elasticsearch - Discuss the Elastic Stack
For now, I don’t know a way to suppress those Elasticsearch log messages until Operate removes the
usage of deprecated ELasticsearch components.

Actually, the logging messages of the Elasticsearch client can be suppressed.

In the Operate configuration ‘application.yml’ you add the line:

logging.level.org.elasticsearch.client.RestClient: ERROR

In future versions, Operate will use another Elasticsearch client, so this configuration should then be obsolete.

Best regards,

Ralf

1 Like