Legacy Knowledge Base
Published Jun. 30, 2025

The portal is not reindexing because the following error: "HTTP/1.1 413 Request Entity Too Large"

Written By

Lucas Mesquita

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

  • When attempting to reindex the portal, the process fails, and the following messages are displayed in the logs:
    May 29 12:46:07.767 build-3886 liferay[liferay-5655d97f59-99cjk] [dxp] ERROR [liferay/background_task-2][SearchEngineInitializer:168] Error encountered while reindexing
    May 29 12:46:07.767 build-3886 liferay[liferay-5655d97f59-99cjk] java.util.concurrent.ExecutionException: com.liferay.portal.kernel.search.SearchException: java.lang.RuntimeException: org.elasticsearch.ElasticsearchStatusException: ElasticsearchStatusException[Unable to parse response body]; nested: ResponseException[method [POST], host [http://search:9200], URI [/_bulk?refresh=true&timeout=1m], status line [HTTP/1.1 413 Request Entity Too Large]_]; [Sanitized]

Environment

  • Liferay PaaS

Resolution

  • This behavior indicates that the content you are trying to reindex is too large.
  • To resolve this issue, it is necessary to remove the file that is too large to reindex (Elasticsearch does not reindex values larger than 100MB by default)
  • Or adjust the following environment variable: ES_SETTING_HTTP_MAX__CONTENT__LENGTH (The value of the variable depends on the size of the archive).

Additional Information

 

 

 

Did this article resolve your issue ?

Legacy Knowledge Base