Details
-
Bug Report
-
Resolution: Done
-
L3 - Default
-
3.6.5, 3.7.0, 3.7.1, 3.7.2, 3.7.3
-
2
-
Not defined
Description
Brief summary of the bug. What is it ? Where is it ?
With Elasticsearch 7.16.0 the request parameter ignore_throttled got deprecated see https://github.com/elastic/elasticsearch/pull/77479 .
The Elasticsearch RestClient used by Optimize sets this parameter by default though causing deprecation warning returned by the Elastic node.
Steps to reproduce:
Run Optimize 3.6.5 or 3.7.0/1 on Elasticsearch 7.16.2+
Actual result :
Observe frequent WARN logs in the optimize log on mapping update (during startup) as well as refresh requests (issued by the import pipeline):
[main] WARN org.elasticsearch.client.RestClient - request [PUT https://elasticsearch:9200/optimize--collection_v4/_mapping?master_timeout=30s&ignore_unavailable=false&expand_wildcards=open%2Cclosed&allow_no_indices=false&ignore_throttled=false&timeout=30s] returned 1 warnings: [299 Elasticsearch-7.16.2- "[ignore_throttled] parameter is deprecated because frozen indices have been deprecated. Consider cold or frozen tiers in place of frozen indices."] 08:19:02.552 [EngineImportScheduler-1] WARN org.elasticsearch.client.RestClient - request [POST http://localhost:9200/optimize-process-definition/_refresh
Expected result:
The deprecated param shouldn't be sent and no warn log issued.
To clarify:
We have tests that check for any warnings during startup/update, why haven't these catched the issue? (Are they only performed for the minimum elastic version?)
Hint:
Either requires a change of client config or a client update if acceptable.