Legacy Knowledge Base
Published Jun. 30, 2025

Elasticsearch Errors - Failure in Bulk Execution and Parsing

Written By

Kenny Back

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

  • We upgraded Elasticsearch and now when we try to re-index JournalArticles we are seeing the following Elasticsearch errors:
ERROR: = failure in bulk execution [liferay-12345], type [LiferayDocumentType], 
id [com.liferay.journal.model.JournalArticle_PORTLET_12345], message [Sanitized]
[ElasticsearchException] [type=mapper_parsing_exception] = failed to parse
[icu_collation_keyword] for [ddmFieldValueKeyword_en_US_String_sortable]]]]_[0]: index

Environment

  • DXP 7.0
  • DXP 7.1
  • DXP 7.2
  • DXP 7.3
  • DXP 7.4

Resolution

  • 'Parse' and 'Failure in Bulk' exceptions often relate to the Elasticsearch analyzer plugins normally installed alongside Elasticsearch. Perform the following steps to reset them:

    1. Uninstall and then re-install the  Analyzers  on all Elasticsearch Nodes.
    2. Restart Elasticsearch.
    3. Clear Liferay Internal Cache.   (For reference:Control Panel > Server Administration > Cache Actions > Execute all Four Options)
    4. Restart Liferay.
    5. Re-index. 

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base