Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

WARN message that includes frozen indices have been deprecated

Written By

Sivakumar Perumal

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • The below WARN message is observed continuously in the Liferay logs   
    WARN  [https-jsse-nio-8443-exec-62][RestClient:65] request [HEAD http:172.17.0.4:9200/liferay-20097-search-tuning-rankings?ignore_throttled=false&include_type_name=true&ignore_unavailable=false&expand_wildcards=open&allow_no_indices=true] returned 1 warnings: [299 Elasticsearch-7.17.5-SNAPSHOT-8d61b4f7ddf931f219e3745f295ed2bbc50c8e84 "[ignore_throttled] parameter is deprecated because frozen indices have been deprecated. Consider cold or frozen tiers in place of frozen indices."]

Environment

  • Elasticsearch 7.17.5
  • Liferay DXP 7.3 and 7.4

Resolution

  • The above WARN message is observed due to the frozen indices feature of Elasticsearch has been deprecated starting the 7.14 version.  Also, this can be ignored as it is a warning that indicates the frozen indices feature has been deprecated and this doesn’t have anything to do with Liferay.

Additional Information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?