"[ignore_throttled] parameter is deprecated because frozen indices have been deprecated

[Archana_Punia]

Continuing the discussion from Ignore_throttled parameter is deprecated:

Hi,

I upgrade my ES and Kibana version to 7.16.3 from 7.15.0 and post upgrading, this warning is showing on my kibana continuously. Can you let me know how to get rid of these warnings?

[warkolm (Mark Walkom)]

Welcome to our community!

See Unfreeze index API | Elasticsearch Guide [8.1] | Elastic. Basically in 8.X you can't freeze an index, so you need to move off this

[joschi]

@warkolm

Basically in 8.X you can't freeze an index, so you need to move off this

Are you saying that we cannot use Elasticsearch 7.15.x, 7.16.x, 7.17.x if we do not want to see this deprecation warning (even if we're not using frozen indices)?

Coming from Default IndicesOptions in SearchRequest and disable specific deprecation warnings this feels weird.

[warkolm (Mark Walkom)]

@joschi

Are you saying that we cannot use Elasticsearch 7.15.x, 7.16.x, 7.17.x if we do not want to see this deprecation warning (even if we're not using frozen indices)?

Uhh, not sure how you got that sorry?
You won't get a deprecation logged for something you aren't using.

[joschi]

@warkolm

Uhh, not sure how you got that sorry?

Unfortunately that's exactly what's happening when using ES 7.16.0 or higher and the Java High Level REST Client (even in the same version).

Default IndicesOptions in SearchRequest and disable specific deprecation warnings

@DavidTurner Yes, we're using the Java High Level REST Client in version 7.16.3. I would not have expected that it's causing the deprecation warning without any possibility whatsoever to disable it, either by not sending the deprecated parameter or by disabling the warning message. So out of the box you cannot use Elasticsearch 7.16.x or later with the Java High Level REST Client without producing the deprecation warning, which makes up ~95% of log messages in our ES clusters. …

Sorry for hijacking this thread, I'll stop posting in this topic now.